DO NOT REPLY [Bug 30652] - Allow configuration of SO_LINGER

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 30652] New: - Allow configuration of SO_LINGER

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

RE: Unable to parse header: HTTP/1.0 200 OK

Mathias It appears to be a problem with the server side script. Some badly written CGI scripts generate HTTP status line + response headers in addition to those automatically generated by the web server. If you produced the wire log of the session that exhibits the problem, I'd be able to tell

Re: Unable to parse header: HTTP/1.0 200 OK

Oups, I'm confused. I've just seen that somebody have post a similar message with exactly the same subject ... Mathias Cianci a écrit : Yes, it's mathias again :o) I get this error message : INFO: Recoverable exception caught when processing request 13 ao¹t 2004 14:25:40 org.apache.commons.httpcl

Unable to parse header: HTTP/1.0 200 OK

Yes, it's mathias again :o) I get this error message : INFO: Recoverable exception caught when processing request 13 ao¹t 2004 14:25:40 org.apache.commons.httpclient.HttpMethodBase processRequest ATTENTION: Recoverable exception caught but MethodRetryHandler.retryMethod() returned false, rethrowi