| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note that this commit has currently only been tested on Linux.
It might be incomplete for other platforms.
|
|
|
|
The path segments . and .. are now removed according to the
rules found in RFC3986.
The path segments are now percent-decoded using the correct
algorithm (the one in RFC3986 and not the "query string" one).
|
|
The If-Modified-Since and If-Unmodified-Since headers are
only used when If-None-Match or If-Match were not found,
respectively. The latter are preferred by the standard
and the former is only there for compatibility with older
clients.
|
|
Was badly implemented previously.
|
|
Weak Etag never matches.
|
|
It only serves to pollute logs.
|
|
|
|
|
|
|
|
The stream handler is responsible for sending errors.
The protocol should only send errors when no responses
were sent (this might not work yet).
|
|
|
|
|
|
|
|
|
|
I will do more breaking changes before documenting more.
|
|
|
|
|
|
|
|
One category of tests involving the SETTINGS ack still fails.
It is probably wise to leave these until more SETTINGS related
tests are written.
|
|
|
|
The same edge cases that fail with other handshake methods
also fail here (mostly bad preface/timeouts stuff). In
addition, the HTTP2-Settings header contents are currently
not checked and so the related edge case tests also fail.
|
|
Currently only testing handshake.
Tests that pass currently involve no request/response.
ALPN and prior knowledge support have some edge cases left to fix.
HTTP/1.1 Upgrade has not been implemented yet.
|
|
|
|
|
|
|
|
Breaking changes with previous commit. This is a very large change,
and I am giving up on making a single commit that fixes everything.
More commits will follow slowly adding back features, introducing
new tests and fixing the documentation.
This change contains most of the work toward unifying the interface
for handling both HTTP/1.1 and HTTP/2. HTTP/1.1 connections are now
no longer 1 process per connection; instead by default 1 process per
request is also created. This has a number of pros and cons.
Because it has cons, we also allow users to use a lower-level API
that acts on "streams" (requests/responses) directly at the connection
process-level. If performance is a concern, one can always write a
stream handler. The performance in this case will be even greater
than with Cowboy 1, although all the special handlers are unavailable.
When switching to Websocket, after the handler returns from init/2,
Cowboy stops the stream and the Websocket protocol takes over the
connection process. Websocket then calls websocket_init/2 for any
additional initialization such as timers, because the process is
different in init/2 and websocket_*/* functions. This however would
allow us to use websocket_init/2 for sending messages on connect,
instead of sending ourselves a message and be subject to races.
Note that websocket_init/2 is optional.
This is all a big change and while most of the tests pass, some
functionality currently doesn't. SPDY is broken and will be removed
soon in favor of HTTP/2. Automatic compression is currently disabled.
The cowboy_req interface probably still have a few functions that
need to be updated. The docs and examples do not refer the current
functionality anymore.
Everything will be fixed over time. Feedback is more than welcome.
Open a ticket!
|
|
[ci-skip]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also convert to AsciiDoc while we're at it.
|
|
A few small revisions were made, and Erlang.mk has been updated.
|
|
Consistently use the imperative mood and add link to LFE examples.
|
|
Update README.md
|
|
Replace Kato with Sameroom
|
|
|
