Why does proxying over HTTP modify X-Forwarded-For while AJP does not?
Issue
- Why does proxying over HTTP modify the
X-Forwarded-Forheader while AJP does not? - Can the modification of the
X-Forwarded-Forheader be disabled when proxying over HTTP in httpd? - Seeing the different EWS Access-Log behaviour between AJP and HTTP?
Environment
- JBoss Enterprise Web Server
- Apache httpd
- mod_proxy_http
- mod_cluster
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
