I can certainly understand not wanting to deal with this.  From the
standpoint of an HttpClient user, the tricky part is that I can't think
of a workaround if I still want to be able to work with this site.  The
only option I can think of would be to fork HttpClient and provide my
own fix, which I really have no desire to do.

I guess the question becomes, to what degree should provisions be made
to deal with non-conforming web servers?  HttpClient already does this
to some degree in the way it works with cookies (e.g., a "Compatibility"
setting), among other things.  In this particular case, the server's
response is obviously very flawed, so it may fall outside of this
threshold of scenarios you're willing to deal with.  Again, the trouble
is that I have no way of elegantly handling this in my own code.  If I
want to use HttpClient I simply wouldn't be able to work with this site.

Todd


On Wed, 09 Aug 2006 10:42:42 +0200, "Oleg Kalnichevski"
<[EMAIL PROTECTED]> said:
> On Wed, 2006-08-09 at 10:34 +0200, Ortwin Glück wrote:
> > Oleg,
> > 
> > Of course I agree. But I remember that we had seen this before. And I 
> > thought that there was code to check for duplicate status lines. But I 
> > can't seem to remember any details. Does anyone know more?
> > 
> > Odi
> > 
> 
> We have seen something similar a couple of years ago. This kind of
> problem is not that uncommon, especially in HTTP responses generated by
> CGI scripts. As far as I remember the argument was all about "common
> browsers tolerate such protocol violations", which I personally do not
> find very convincing
> 
> Oleg
> 
> 
> > Oleg Kalnichevski wrote:
> > > Todd,
> > > 
> > > The request head is completely messed up. Note second instance of the
> > > status line (HTTP/1.1 200 OK) between Date and Content-Type headers.
> > > HttpClient is absolutely correct in rejecting this request as malformed
> > > 
> > > Oleg
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to