Arno Garrels wrote: > Maurizio Lotauro wrote: >> Scrive "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>: >> >> [...] >> >>> However, I wonder how this works in practice. I >>> mean, how do regular browsers deal with it? >> >> Good question. Someone that know the html can prepare a page with a >> text box where write the content to send and a post button? >> It will be very useful, not only in that case. > > I've uploaded a Wireshark dump file: > http://www.duodata.de/misc/PostAuthLog.zip > > It's IE trying to upload a file to IIS 5.1 and basic authentication is > required. Logging stopps when the authentication dialog in IE popped > up. There is no chunked encoding used and the connection isn't closed > even though IE sent the content-length. If anybody can read this log, > please post your ideas.
Well, it does not show the case we are are discussing here. Would be usefull to have a packet dump that shows the problem in question. And another one with IE as the client. -- Arno > > -- > Arno > > >> >>> The RFC >>> specifically states that if you receive an error >>> after the headers, and you used a Content-Length >>> header, you MUST (their emphasis) drop the connection. >> >> Should the 401 be considered an error? >> >>> Perhaps it's done with "chunking"? >> >> At this point I would like to see how a browser handle this situation >> before going ahead with the component. I'm waiting for an html form >> :-) >> >> >> Bye, Maurizio. >> >> ---------------------------------------------------- >> This mail has been sent using Alpikom webmail system >> http://www.alpikom.it -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be