Thus wrote dl,
>> It would be interesting to see an actual HTTP message to understand
>> what causes the protocol violation.
>>
> Is there a way to make WebClient dump that debug info? It doesn't
> load anything into ResponseHeaders before the error happens, and
> because of the SSL encryption I can't read anything in Ethereal.
Sorry, I really missed the SSL part. You can always do it with a browser
plugin like LiveHttpHeaders for Firefox -- it runs after decryption.
>> Note that you can always code your own dirty litte HTTP client using
>> Sockets or TcpClient.
>>
> I guess I'm kind of worried how long it would take to get SSL
> implemented if I went this route. Do sockets or tcpclient handle
> this?
.NET 2.0 comes with SslStream. For .NET 1.1 you have to use a third party
solution like Mentalis.org.
Cheers,

Signature
Joerg Jooss
news-reply@joergjooss.d
DL - 20 Mar 2006 14:16 GMT
>Thus wrote dl,
>
[quoted text clipped - 7 lines]
>Sorry, I really missed the SSL part. You can always do it with a browser
>plugin like LiveHttpHeaders for Firefox -- it runs after decryption.
Thank you for the reference to LiveHttpHeaders. I realized by looking
at the post data that I was overlooking some javascript code that does
some MD5 calculation before posting back to the server. It still
throws a ServerProtocolViolation exception, but the post occurs and
access is granted to the administrative pages of the router.
-DL