| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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
|
|
|
|
|
|
I noticed that this appeared to point to a bad URL. If LeoFS is sponsoring this, they'd probably prefer having the right URL.
|
|
|
|
|
|
Fixes #839 when 'Connection: Keep-Alive' wasn't sent in a HTTP/1.0
response. Now the usage of 'Connection' header is consistent with
current protocol version: when this header is not specified explicitly
in the response, HTTP/1.0 implies 'Connection: close' and HTTP/1.1
implies 'Connection: Keep-Alive'. So if current 'Connection' value
matches the default value of current protocol, we won't state obvious
fact in the response; and vice versa.
Amended to fix and improve tests, and revert the variable name
change from HTTP11Headers to StdHeaders. I think it's still good
to leave it as is because it's not really a standard header for
HTTP/1.0, and it's gone from HTTP/2 entirely.
|
|
Mostly useful for REST, which has a ton. This is an initial
commit, it still needs to be tested, but it's time to sleep.
|
|
Yes I know the function never returns. :-)
|
|
|
|
Avoids unnecessary calculations.
|
|
In the eventsource example.
|
|
[ci skip]
|
|
|
|
|
|
Looks like I pushed too early in the previous commit. Oops!
|
|
cowboy_stream_h isn't in the repository yet.
|
|
Let's try this [ci skip] stuff.
|
|
|
|
|
|
|
|
|
|
|
|
To be kept after the run ends.
|
|
The best way to use 'make ci' is 'make -k ci', then it
will complete its run even if a version fails, and still
exit with an error code.
|
|
Unfortunately not seeing how I can try it other than committing
the file... Oh well, polluting the logs!
|
|
|
|
Everything is now directly generated from the Makefile.
Also properly update dependencies.
|
|
|
|
|
