Marek
Related: sockjs/sockjs-protocol#57
`cowboy_http_req` got renamed to `cowboy_req`. This is quite bad as changing that would break compatibility with older cowboy. Quick workaround: ``` $ sed -i 's/cowboy_http_req/cowboy_req/g' src/sockjs_http.erl ```
Also @yrashk had already done the port: https://github.com/spawngrid/sockjs-erlang/tree/cowboy-master
@yrashk Are there changes similar to b19ead66e847b149c9ccad5ffc837e58eb283c34 that could be ported to mainline without breaking compatibility with R14 _and_ older cowboy?
The changes seem to be: 1. cowboy_http_req -> cowboy_req 2. new dependency - ranch 3. instead of cowboy:start_http we have cowboy:start_listener 4. casing of headers (camelcase vs lowercase) (can you...
@yrashk I've noticed you forked `master` branch, not `dev`, therefore sockjs-protocol-dev.py fails in few more places. Could you take a look? I don't think there are many changes included on...
BTW, AFAICT behaviour of version:7 is nearly identical to version:8
Here: http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-07
Right. Just a quick dig through rfc: Section 14.13 of RFC2616 http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html > Applications SHOULD use this field to indicate the transfer-length of the message-body, unless this is prohibited by...
Nope. I'm talking about the 3rd case.