Todd,
The question is not *how* to handle this in your code, but rather *if*!
That system is not speaking HTTP, but something else. Why bother at all?
If you can, you should speak to the operators of that system and make
them comply with the (at least the basic) HTTP standard.
Odi
Todd Wilson wrote:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
