Simon Fell > Its just code > HttpWebRequest
Dare has a rant on HttpWebRequest. I remember having to jump through similar hoops for the 301 support in Aggie. Also it appears that HttpWebRequest isn't handling persistent connections properly, in that if the server closes the connection before the client expects it, you end up with it throwing an exception when you try and re-use the connection to send the next request. I'd expect it to notice that the server has closed the connection and siliently open a new one, this is what every other HTTP 1.1 client stack I've looked at does.