Not All Headers Can Be Captured in Access.log File
(Doc ID 1935751.1)
Last updated on AUGUST 19, 2022
Applies to:
Oracle API Gateway - Version 11.1.1.6.1 to 11.1.2.4.0 [Release 11gR1]Information in this document applies to any platform.
Symptoms
Access log settings are being configured as per API Gateway Documentation.
This works, but certain headers are not logged in the access.log file in spite of using the correct Format String as per Apache Module mod_log_config - Custom Log Formats.
For example, the following seems to be working:
"%{Host}o"
"%{Accept}i"
"%{Accept}o"
"%{User-agent}i"
"%{User-Agent}o"
"%{Accept}i"
"%{Accept}o"
"%{User-agent}i"
"%{User-Agent}o"
However, the following does not seem to work:
"%{X-CorrelationID}o"
"%{Date}o"
"%{Connection}i"
"%{Connection}o"
"%{Content-Type}o"
"%{Date}o"
"%{Connection}i"
"%{Connection}o"
"%{Content-Type}o"
Changes
Enabling/changing the pattern for the Access.log.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |