[Mono-bugs] [Bug 50530][Min] Changed - Authenticated POST requests do not work with HTTP/1.0 servers

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 29 Jan 2004 20:32:11 -0500 (EST)


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by helge.hess@opengroupware.org.

http://bugzilla.ximian.com/show_bug.cgi?id=50530

--- shadow/50530	2004-01-29 20:18:47.000000000 -0500
+++ shadow/50530.tmp.16916	2004-01-29 20:32:11.000000000 -0500
@@ -1,13 +1,13 @@
 Bug#: 50530
 Product: Mono/Class Libraries
 Version: unspecified
 OS: SuSE 8.1
 OS Details: 
-Status: RESOLVED   
-Resolution: FIXED
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
 Priority: Minor
 Component: Sys.Web
 AssignedTo: gonzalo@ximian.com                            
 ReportedBy: helge.hess@opengroupware.org               
 QAContact: mono-bugs@ximian.com
@@ -136,6 +136,35 @@
 
 <?xml version='1.0'?>
 <a></a>
 ---snap---
 
 Where is my authenticate header? I requested one using Preauthenticate?
+
+------- Additional Comments From helge.hess@opengroupware.org  2004-01-29 20:32 -------
+OK, I think its valid to reopen the issue (shame on me if not! ;-)
+
+Setting the httpVersion to 1.0 doesn't help at all:
+---snip---
+        webRequest.ProtocolVersion=HttpVersion.Version10;
+---snap---
+
+The only thing this does is setting the request method to 1.0! It
+still issues the expect: 100-continue header which is inappropriate in
+an HTTP/1.0 context (though the processing should actually be the same
+for 1.0 and 1.1 as far as I can see):
+---snip---
+POST /RPC2 HTTP/1.0
+Content-Type: text/xml
+Content-Length: 30
+Expect: 100-continue
+Connection: keep-alive
+Host: localhost
+---snap---
+http://ftp.ics.uci.edu/pub/ietf/http/rfc1945.html
+
+The result is exactly the same, no Preauthenticate support and a
+timeout due to the 100-continue.
+
+
+Could you please explain what exactly you fixed in CVS? Is it possible
+that the fix is not in 0.29 even though it was released after your fix?