Skip to content
Snippets Groups Projects
Commit dbfbbb41 authored by Andy Green's avatar Andy Green
Browse files

user code must explicitly complete http transaction

parent 5c0bcf49
Branches
No related tags found
No related merge requests found
...@@ -17,6 +17,17 @@ known to affect anything until after it was fixed ...@@ -17,6 +17,17 @@ known to affect anything until after it was fixed
requests callback on writeable for the socket it will busywait until the requests callback on writeable for the socket it will busywait until the
socket closes socket closes
5) MAJOR Although the test server has done it for a few versions already, it
is now required for the user code to explicitly call
if (lws_http_transaction_completed(wsi))
return -1;
when it finishes replying to a transaction in http. Previously the library
did it for you, but that disallowed large, long transfers with multiple
trips around the event loop (and cgi...).
Changes Changes
------- -------
......
...@@ -130,7 +130,7 @@ lws_read(struct lws *wsi, unsigned char *buf, size_t len) ...@@ -130,7 +130,7 @@ lws_read(struct lws *wsi, unsigned char *buf, size_t len)
switch (wsi->state) { switch (wsi->state) {
case LWSS_HTTP: case LWSS_HTTP:
case LWSS_HTTP_HEADERS: case LWSS_HTTP_HEADERS:
goto http_complete; goto read_ok;
case LWSS_HTTP_ISSUING_FILE: case LWSS_HTTP_ISSUING_FILE:
goto read_ok; goto read_ok;
case LWSS_HTTP_BODY: case LWSS_HTTP_BODY:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment