diff options
| author | Azat Khuzhin <a3at.mail@gmail.com> | 2016-02-15 00:12:54 +0300 |
|---|---|---|
| committer | Azat Khuzhin <a3at.mail@gmail.com> | 2016-03-09 18:52:07 +0300 |
| commit | 9fde5189df2722bf58041f03a9d0b69c87dffa8b (patch) | |
| tree | 1cfcc6fff4247b87cede6e9e1df0dce322ba680b /http-internal.h | |
| parent | 680742e1665b85487f10c0ef3df021e3b8e98634 (diff) | |
| download | libevent-9fde5189df2722bf58041f03a9d0b69c87dffa8b.tar.gz | |
http: lingering close (like nginx have) for entity-too-large
By lingering close I mean something what nginx have for this name, by this term
I mean that we need to read all the body even if it's size greater then
`max_body_size`, otherwise browsers on win32 (including chrome) failed read the
http status - entity-too-large (while on linux chrome for instance are good),
and also this includes badly written http clients.
Refs: #321
v2: do this only under EVHTTP_SERVER_LINGERING_CLOSE
Diffstat (limited to 'http-internal.h')
| -rw-r--r-- | http-internal.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/http-internal.h b/http-internal.h index ba6e49ef..31002e0d 100644 --- a/http-internal.h +++ b/http-internal.h @@ -154,6 +154,7 @@ struct evhttp { size_t default_max_headers_size; ev_uint64_t default_max_body_size; + int flags; const char *default_content_type; /* Bitmask of all HTTP methods that we accept and pass to user |