4 ms·

Sounds like you have a very picky feed reader. Which one is it? And what specifically is it complaining about? Does anyone know if the http protocol actually

by pg 17y ago

Sounds like you have a very picky feed reader. Which one is it? And what specifically is it complaining about? Does anyone know if the http protocol actually mandates more header lines than we're supplying?

sarvesh 17y ago
Hard to say without the request but he may be doing persistent http connection (keep-alive) in which case content-length is required.
sayrer 17y ago
Hmm, it is complaining about the status line (the first one). I think it is choking on the HTTP 1.0 response with a Connection header. That header was added in HTTP 1.1, but lots of people use it with HTTP 1.0 and pretty much everyone supports it. (edit: by which I mean they ignore it, because connection: close is the default behavior in HTTP 1.0) That said, you should add an ETag to the response. Hacker News changes often enough that timed expiration won't help, but ETags might get you a lot of 304 Not Modified responses.
- pg 17y ago
  So if I just change the current header to say HTTP 1.1 am I done, or does that require additional changes?
  - deleted 17y ago
    [deleted]
  - sayrer 17y ago
    It doesn't require additional changes. I'm not sure it will fix the .NET client library's paranoia though--I was only guessing.
pj 17y ago
I'm using the .net HTTP libraries. Not a specific feed reader, rather I'm pulling in the XML and parsing it out. Here's a thread from somewhere else about the issue. http://channel9.msdn.com/forums/TechOff/257803-HttpWebRequestResponse-The-server-committed-a-protocol-violation-SectionResponseStatusLine/ http://channel9.msdn.com/forums/TechOff/257803-HttpWebReques... When I added the web.config setting, as explained in the article, it works: <system.net> <settings> <httpWebRequest useUnsafeHeaderParsing="true" /> </settings> </system.net> I think I remember a similar issue from the past related to a missing content-length header.

by pg 17y ago

sarvesh 17y ago

Hard to say without the request but he may be doing persistent http connection (keep-alive) in which case content-length is required.

sayrer 17y ago

Hmm, it is complaining about the status line (the first one). I think it is choking on the HTTP 1.0 response with a Connection header. That header was added in HTTP 1.1, but lots of people use it with HTTP 1.0 and pretty much everyone supports it. (edit: by which I mean they ignore it, because connection: close is the default behavior in HTTP 1.0) That said, you should add an ETag to the response. Hacker News changes often enough that timed expiration won't help, but ETags might get you a lot of 304 Not Modified responses.

pg 17y ago
So if I just change the current header to say HTTP 1.1 am I done, or does that require additional changes?
- deleted 17y ago
  [deleted]
- sayrer 17y ago
  It doesn't require additional changes. I'm not sure it will fix the .NET client library's paranoia though--I was only guessing.

pj 17y ago

I'm using the .net HTTP libraries. Not a specific feed reader, rather I'm pulling in the XML and parsing it out. Here's a thread from somewhere else about the issue. http://channel9.msdn.com/forums/TechOff/257803-HttpWebRequestResponse-The-server-committed-a-protocol-violation-SectionResponseStatusLine/ http://channel9.msdn.com/forums/TechOff/257803-HttpWebReques... When I added the web.config setting, as explained in the article, it works: <system.net> <settings> <httpWebRequest useUnsafeHeaderParsing="true" /> </settings> </system.net> I think I remember a similar issue from the past related to a missing content-length header.