Curzio.Dellasanta at Sun
May 16, 2008, 6:22 AM
Post #1 of 2
(77 views)
Permalink
|
|
100-continue response when 3xx expected - Apache 2.2.26
|
|
Hi,
I see a difference in the way Apache responds to a Expect:
100-continue header in version 1.3.28 vs 2.2.6. The 1.3.28 handling is
correct. I feel the 2.2.6 handling is a bug.
For PUT requests with a Expect: 100-continue header, Apache 2.2.6
server sends a HTTP/1.1 100 Continue response before checking to see
if a 3xx response (redirect) might need to be sent for the request.
The client ends up sending the entire PUT or POST body in response to
the 100 continue only to have it be ignored by the server due to a
3xx.
This defeats the purpose of the continue response stated in the HTTP 1.1
RFC - http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.2.3
Pretty the same issue was reported by ragini.bisarya on Oct 15 2007 for
4xx responses .. see Bug
https://issues.apache.org/bugzilla/show_bug.cgi?id=43711
Looking at the patch provided for the 4xx bug I doubt it solves this
issue too, but I've no resources to check this out.
To reproduce this you can issue a "curl -v -L -T [file] [url to an
apache2.2 server redirected page]"
Should I file a new bug for this?
Greetings,
Curzio
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe[at]httpd.apache.org
" from the digest: users-digest-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: users-help[at]httpd.apache.org
|
