Bug 44730

Summary: duplicate query string in remote server url when using "nocanon" reverse proxy
Product: Apache httpd-2 Reporter: Wil Tan <wil>
Component: mod_proxyAssignee: Apache HTTPD Bugs Mailing List <bugs>
Status: RESOLVED LATER    
Severity: normal Keywords: MassUpdate, PatchAvailable
Priority: P2    
Version: 2.2.8   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Attachments: Proof-of-concept that fixes the issue

Description Wil Tan 2008-04-01 10:58:29 UTC
I have the following config:

<VirtualHost *:80>
    ServerName alpha.xri.net
    ProxyRequests Off
    ProxyPass / http://localhost:8003/ nocanon
    ProxyPassReverse / http://localhost:8003/
    ErrorLog logs/alphaxriproxy-error_log
    CustomLog "|/usr/sbin/cronolog /usr/local/apache2/logs/alphaxriproxy.log.%Y-%m-%d" combined
</VirtualHost>


When a request comes in to the local server:

http://alpha.xri.net/proxy/=kermit*%E6%97%A5%E6%9C%AC%E7%89%88?_xrd_r=application/xrds+xml

the mapped remote server URL became:

http://localhost:8003/proxy/=kermit*%E6%97%A5%E6%9C%AC%E7%89%88?_xrd_r=application/xrds+xml?_xrd_r=application/xrds+xml

This seems to happen when "nocanon" is turned on.

This is related to bug 41798.
Comment 1 Wil Tan 2008-04-01 11:02:27 UTC
Created attachment 21755 [details]
Proof-of-concept that fixes the issue

This seems to be due to the code handling the "nocanon" option using r->unparsed_uri instead of r->uri. The r->unparsed_uri contains the query string while r->uri does not.

This patch excludes the query portion of r->unparsed_uri when constructing the remote server URL.
Comment 2 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.