https://issues.apache.org/bugzilla/show_bug.cgi?id=47087
--- Comment #12 from Sven Mueller <[email protected]> 2009-12-15 04:39:41 UTC --- (In reply to comment #10) > Disabling keepalive unconditionally for all requests which include Expect: > 100-continue is overkill. I think it would be sufficient to fix this bug to > disable keepalive when sending a final response, if the client has sent > "Expect: 100-continue", and no 1xx interim response has already been sent. > > RFC 2616 lists that as a "MAY" if I interpret section 8.2.3 correctly. As I was asked in https://issues.apache.org/bugzilla/show_bug.cgi?id=46709#c3 wether I would be able to test drive this patch: No, not at the moment. It might be possible again in early 2010 (i.e. end of February, begin of March). Anyhow, as far as I understood from the discussion, this patch disables keepalive for any response but "100 Continue", which means the connections are closed after the final response. Unfortunately, this would cause troubles here, as we found out. Some of the clients simply don't reconnect when they asked for a keep-alive session. If they get a disconnect with the non-100 response, they seem to report an error. Please note that I don't have access to the client sources, and probably will never have that access. I just know a few facts about them: They use the .Net framework, don't authenticate on first try (as a means to find out how to authenticate), request keep-alive and 100-continue. The rest differs: Some clients correctly reconnect on no-keepalive, some don't. Some handle a 417 return code correctly, some don't..... -- 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]
