DO NOT REPLY [Bug 18266] New: - https file upload via proxy

[bu...@apache.org]

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=18266>.
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=18266

https file upload via proxy

           Summary: https file upload via proxy
           Product: Apache httpd-1.3
           Version: 1.3.27
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_proxy
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: neil.wilkinson@transport.nsw.gov.au


Using mod_proxy as part of the 1.3.27 distribution of apache.

When trying to upload a file to a https website via an apache proxy, the 
browser fails.  Different browsers give different errors - MSIE gives a 'Cannot 
find server or DNS Error' page, netscape v4.8 says 'connection reset by peer'.  
(I've noticed that MSIE always gives that error no matter what the problem.)

Seems odd given that https proxying is completely transparent.  i.e. it just 
connects the client->proxy connection with the proxy->server with no 
interference, right?  This error only occurs with file uploads - i.e. when the 
request buffer is larger than usual.

This error occurs when using a apache as a proxy to another apache internal 
server and also when using an external site running Microsoft-IIS/5.0.

I wish i could give a url to recreate this bug but of course the pages are 
secure for a good reason :)

A way to recreate this page is to host the following html on a https server 
(called test.html) and then use an apache server as a proxy from your browser:

<form action="test.html" method="POST" enctype="multipart/form-data">
<input type="file" name="test_file"/>
<br/>
<input type="submit"/>
</form>

If you get a "Method not allowed" then that is fine because the file has been 
uploaded to a page which is not dynamic but at least the http request has 
finished in that case.

The error when proxying appears so quickly, that I am sure that there has not 
been enough time to send the entire request.

To whomever looks after these bugs:  thanks - apache has the least bugs in any 
software I have ever found.  I've been using it for years and this is my first 
bug :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org