https://issues.apache.org/bugzilla/show_bug.cgi?id=47087
--- Comment #1 from Stuart A. Malone <[email protected]> 2009-08-27 09:22:42 PDT --- I also ran into this bug when trying to write a simple WebDAV client using Microsoft's .NET Framework. I have a very simple C# test program that demonstrates the problem, and have Wireshark network traces that demonstrate that the error is in Apache rather than .NET. You can read the discussion and find links to the network traces on the MSDN forums at: <http://social.msdn.microsoft.com/Forums/en-US/ncl/thread/5c576a2d-2f13-485c-8ada-b4c3ee127d3c/> I just re-ran the test against Apache 2.2.13 on Mac OS X Snow Leopard, and the problem is still there. It appears that Apache is violating this paragraph from RFC 2616: - Upon receiving a request which includes an Expect request-header field with the "100-continue" expectation, an origin server MUST either respond with 100 (Continue) status and continue to read from the input stream, or respond with a final status code. The origin server MUST NOT wait for the request body before sending the 100 (Continue) response. If it responds with a final status code, it MAY close the transport connection or it MAY continue to read and discard the rest of the request. It MUST NOT perform the requested method if it returns a final status code. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
