…g if some evil code tries to feed socket_loop with unsupported messages. This way tcp messages other than tcp_closed and ssl_closed are saved until request/2 is called (if it is a keep_alive connection) so if client decides to reuse a connection (which is possible in HTTP/1.1) it won't have data eaten by _Else clause. Instead of being too forgiving, its connection will be rather forcefully dropped (if it was a keep_alive connection) next time request/2 is called, which is a right way to penalize an unruly code.
…_closed) and quit immediately, because is no sense in trying to send anything to the closed socket.
minor bug corrections
…io veiga) * added support to multiple websocket draft protocols (for backwards compatibility) * added ws_autoexit option which allows to get an event on websocket controlling processes (issue track #15, suggestion of esente) * added headers also in misultin websockets (thanks to jlirochon) * made it basho's rebar friendly (thanks to mrinalwadhwa)
bug correction on Content-Length: 0 header causing timeout on POST requests [issue track #12, thanks to gdamjan]
… thanks to Max Lapshin] - added support to standard http headers response - added http 400 bad request error in socket handling - bug correction: removed erroneous sending of response timeout on listening open connections - added stream_support optimization option