You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/07/02 13:39:37 UTC
DO NOT REPLY [Bug 21271] New: -
Support for full fixed reverse mappings
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21271>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21271
Support for full fixed reverse mappings
Summary: Support for full fixed reverse mappings
Product: Apache httpd-1.3
Version: 1.3.27
Platform: All
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: mod_proxy
AssignedTo: bugs@httpd.apache.org
ReportedBy: apache@shoenix.net
Currently there is no sane processing for statements like :
ProxyPassReverse https://mysecure.domain/myurl http://mynonsecure.internal/myurl
Statements like this should be considered as fixed, full URLs and the relative
URL construction (ap_construct_url()) should be omitted in these cases. This
issue was located because we have an external SSL accelerator (not maintaned by
us :( ) which handles the SSL and forwards to non-secure internal hosts. For
the original reverse mappings it would always construct the URL from the server
config, which is configured for 'http'. Since the http -> https rewrites do not
happen in the SSL accel. (dont ask!) we want to make sure we rewrite to https
ourselves. This, together with the fact there is no sane handling anyway this
seems like a good idea.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org