Bug 46534 - mod_proxy_ajp scheme and port do not follow UseCanonicalPhysicalPort
Summary: mod_proxy_ajp scheme and port do not follow UseCanonicalPhysicalPort
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy_ajp (show other bugs)
Version: 2.2.11
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate, PatchAvailable
Depends on:
Blocks:
 
Reported: 2009-01-14 20:06 UTC by Robert Egglestone
Modified: 2018-11-07 21:08 UTC (History)
1 user (show)



Attachments
Use ap_http_scheme and ap_get_server_port to determine the scheme and port (1.44 KB, patch)
2009-01-14 20:06 UTC, Robert Egglestone
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Egglestone 2009-01-14 20:06:32 UTC
Created attachment 23119 [details]
Use ap_http_scheme and ap_get_server_port to determine the scheme and port

At present mod_proxy_ajp will always send through the real scheme and port of the request through to a backend server. If the backend server wishes to perform a redirect, then the client will be redirected to the wrong place.


For example, I'm using SSL offload appliance sitting in front of Apache, and Apache receives http on either 80 or 81 for normal or secure. At present, Apache will send http+81 through to the backend server, however with UseCanonicalName off, UseCanonicalPhysicalPort off, and a ServerName of "https://....:443", I believe it should be going through as https+443. (Following the advice given in http://httpd.apache.org/docs/2.2/mod/core.html#servername)


The attached patch makes use of the ap_http_scheme and ap_get_server_port functions, so that the UseCanonicalX directives are respected.
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:53 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.