It’s not just a nit: SharpReader refuses to process feeds with the invalid header! Instead it reports “Error reading URL: The underlying connection was closed: The server committed an HTTP protocol violation. ” (I just spent a ridiculous amount of time tracking the problem down to this typo.)
This appears to be fixed in CVS, but broken in 1.2.1.
Anonymous
If you have the .NET framework 1.1 SP1 or later installed and you use a RSS feed reader that is built on .NET, you will get the protocol violation. Apparently, that version and later enhances security and a space in the header at that point could be a possible hacking point.
I’m not sure if it is an actual vulnerability but .NET treats it as such. Here is a bit more detailed fix for the problem.
http://www.garoo.net/en/archives/2004/10/14/182821
A very nice and helpful fellow.
