| Age | Commit message (Collapse) | Author |
|---|
|
We were only reading 1k of data in before, but if a header was more than
1k then we just would give up. Now we read as much as we can that has
loaded into the buffer and if we run out we can try again, but if it's
just a very long header we'll deal with it properly still.
|
|
|
|
It at least seems to!
|
|
|
|
|
|
This is an extra call that happens during the http handshake that allows
the implementation to set additional headers, modify existing headers,
and cancel the whole connection if desired.
|
|
In theory that should be fine, the standard stipulates case, but headers
should be case insensitive in most cases, so now we're more compatible.
Amusingly, browsers and other clients did it correctly, apache doesn't.
|
|
|
|
|
|
|
|
It may not have had as much to do with low-level protocol details, and a
lot of this can be reverted, but I can't revert it right now. I'll look
it over later in the week.
|
|
It would be really cool to add more features, like pre-websocket
negotiation and callbacks for serving web content, etc.
|
