Commit eedfedd1 authored by Sergey Lyubka's avatar Sergey Lyubka

Added reference to a relevant pull request in getreq() comment

parent 87d841d8
...@@ -3649,6 +3649,7 @@ static int getreq(struct mg_connection *conn, char *ebuf, size_t ebuf_len) { ...@@ -3649,6 +3649,7 @@ static int getreq(struct mg_connection *conn, char *ebuf, size_t ebuf_len) {
// The reason for treating GET and POST/PUT differently is that libraries // The reason for treating GET and POST/PUT differently is that libraries
// like jquery do not set Content-Length in GET requests, and we don't // like jquery do not set Content-Length in GET requests, and we don't
// want mg_read() to hang waiting until socket is timed out. // want mg_read() to hang waiting until socket is timed out.
// See https://github.com/cesanta/mongoose/pull/121 for more.
conn->content_len = INT64_MAX; conn->content_len = INT64_MAX;
if (!mg_strcasecmp(conn->request_info.request_method, "GET")) { if (!mg_strcasecmp(conn->request_info.request_method, "GET")) {
conn->content_len = 0; conn->content_len = 0;
......
...@@ -4960,6 +4960,7 @@ static int getreq(struct mg_connection *conn, char *ebuf, size_t ebuf_len) { ...@@ -4960,6 +4960,7 @@ static int getreq(struct mg_connection *conn, char *ebuf, size_t ebuf_len) {
// The reason for treating GET and POST/PUT differently is that libraries // The reason for treating GET and POST/PUT differently is that libraries
// like jquery do not set Content-Length in GET requests, and we don't // like jquery do not set Content-Length in GET requests, and we don't
// want mg_read() to hang waiting until socket is timed out. // want mg_read() to hang waiting until socket is timed out.
// See https://github.com/cesanta/mongoose/pull/121 for more.
conn->content_len = INT64_MAX; conn->content_len = INT64_MAX;
if (!mg_strcasecmp(conn->request_info.request_method, "GET")) { if (!mg_strcasecmp(conn->request_info.request_method, "GET")) {
conn->content_len = 0; conn->content_len = 0;
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment