|Summary:||Problem with accents in filename and byte serving|
|Component:||All||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
Description marc-andre.l 2010-02-02 11:46:39 UTC
Ok so we recently set up and Apache Server for the sole purpose of downloading large PDF files securely with byte-serving. Adobe Reader would launch and we can browse a file while it is downloading in the backgound. So everything was working great except when we tried to download a file with an accent in it ( É ), then the first page of the PDF would load correctly but after that it would hang and Adobe would utlimately show and error 14 (after several minutes). Upon investigation we found the following in the server access log. 184.108.40.206 - - [02/Feb/2010:14:21:41 -0500] "GET /test%20%C3%89.pdf HTTP/1.0" 200 58246434 220.127.116.11 - - [02/Feb/2010:14:21:41 -0500] "GET /test%20%C3%89.pdf HTTP/1.1" 200 58246434 18.104.22.168 - - [02/Feb/2010:14:21:48 -0500] "GET /test%20\xc9.pdf HTTP/1.1" 403 212 22.214.171.124 - - [02/Feb/2010:14:21:48 -0500] "GET /test%20\xc9.pdf HTTP/1.0" 403 212 The first two lines is the request made by us, we can see that the É character was converted to utf-8 and encoded using % sign (%C3%89). The next two lines are request from Adobe Reader to obtain byte ranges, and then the server replied with a 403 status code. You can see that the URL is slightly different (%C3%89 was replaced by \xc9), I don't know if this is the reason for the 403 status code but I don't see what else could be. We also tried the IIS byte serving and it would download the file without an problem (even with an accent in the filename) so it clearly seams to be some problem with the Apache server. If it is something that we can fix in the configuration please tell us what to do since i could not find an reference of this problem anywhere else. Thank you.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:35 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.