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

2004-08-13 Thread Kalnichevski, Oleg
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

2004-08-13 Thread Mathias Cianci
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

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

2004-08-06 Thread Upayavira
Upayavira wrote: Tried that, didn't work. Thanks for your comments. I will now: 1) Contact the site provider, see if they can fix their broken site They said "We have no intention to resolve this at present" 2) Patch a version of HttpClient for my own use until the site fixes their headers So I ch

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

2004-08-06 Thread Upayavira
Ortwin Glück wrote: Upayavira wrote: I'm getting an HttpException: Unable to parse header: HTTP/1.0 200 OK Using a command like the following command: curl -u user:pass -I -i "http://mysite:6998/page.exe?id=2"; I got the following output: HTTP/1.1 200 OK Server: Microsoft-IIS/5.0 Date: Thu,

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

2004-08-05 Thread Ortwin Glück
Upayavira wrote: I'm getting an HttpException: Unable to parse header: HTTP/1.0 200 OK Using a command like the following command: curl -u user:pass -I -i "http://mysite:6998/page.exe?id=2"; I got the following output: HTTP/1.1 200 OK Server: Microsoft-IIS/5.0 Date: Thu, 05 Aug 2004 10:20:32