Configure MDC access for header requests
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Access to HTTP header values as Mapped Diagnostic Context (MDC) fields can be
set using the OEReqHead.xxxxx token, where xxxxx is the HTTP header name (not case sensitive). The
OpenEdge MDC support does not automatically make all HTTP headers available as MDC
values. You must configure the list of header names if that level of information is
required in your log files.
To configure the list of HTTP headers available as MDC fields:
- Edit the PAS for OpenEdge instance instance-name/conf/oeablSecurity.properties file, so the list is available to all deployed ABL applications and their ABL web applications.
- Append the
MDC.filter.headerListproperty with a comma-separated list of header names:MDC.filter.headerList=HeaderName1, HeaderName2Note: Providing invalid header patterns can result in the no creation of the localhost access log. - Save the oeableSecurity.properties
file.
The HTTP request header name is available for use in
%headerfields for the localhost access log in instance-name/conf/logging-tomcat.properties, for example:psc.as.logging.access.pattern=%h %l %reqAttribute{OEReq.userId} [%date{"yyyy-MM-dd'T'HH:mm:ss.SSSXXX"}] "%r" %s %b %reqAttribute{OEReq.requestId} %header{HeaderName1} %header{HeaderName2} %n