On Monday, 19 September 2016 at 18:13:12 UTC, Chris wrote:
On Monday, 19 September 2016 at 17:54:05 UTC, Steven
Schveighoffer wrote:
On 9/19/16 1:34 PM, Chris wrote:
[...]
Here is the culprit:
https://github.com/rejectedsoftware/vibe.d/blob/0.7.29/source/vibe/http/server.d#L1861
And the def
On Monday, 19 September 2016 at 17:54:05 UTC, Steven
Schveighoffer wrote:
On 9/19/16 1:34 PM, Chris wrote:
[...]
Here is the culprit:
https://github.com/rejectedsoftware/vibe.d/blob/0.7.29/source/vibe/http/server.d#L1861
And the definition of MaxHTTPHeaderLineLength is:
https://github.com/r
On 9/19/16 1:34 PM, Chris wrote:
On Monday, 19 September 2016 at 16:55:05 UTC, Steven Schveighoffer wrote:
Hm... you don't get a full stack trace? Hard to tell what max_bytes
should be, it defaults to ulong.max, so no way you are exhausting
that. Without knowing where readUntilSmall is called
On Monday, 19 September 2016 at 16:55:05 UTC, Steven
Schveighoffer wrote:
Hm... you don't get a full stack trace? Hard to tell what
max_bytes should be, it defaults to ulong.max, so no way you
are exhausting that. Without knowing where readUntilSmall is
called, it's hard to diagnose.
-St
On 9/19/16 11:59 AM, Chris wrote:
On Thursday, 15 September 2016 at 13:26:48 UTC, Steven Schveighoffer wrote:
On 9/15/16 9:11 AM, Chris wrote:
On Wednesday, 14 September 2016 at 20:23:09 UTC, Steven Schveighoffer
wrote:
Hm.. I have adjusted this in my project, and it works (set to 50M).
Need
On Thursday, 15 September 2016 at 13:26:48 UTC, Steven
Schveighoffer wrote:
On 9/15/16 9:11 AM, Chris wrote:
On Wednesday, 14 September 2016 at 20:23:09 UTC, Steven
Schveighoffer
wrote:
Hm.. I have adjusted this in my project, and it works (set to
50M).
Needed it for uploading large images
On Friday, 16 September 2016 at 00:35:25 UTC, sarn wrote:
I hope this isn't too obvious, but I have to ask because it's
such a common gotcha:
Are you reverse proxying through a server like nginx by any
chance? There are default request size limits there. (For
nginx specifically, it's this o
I hope this isn't too obvious, but I have to ask because it's
such a common gotcha:
Are you reverse proxying through a server like nginx by any
chance? There are default request size limits there. (For nginx
specifically, it's this one:
https://nginx.org/en/docs/http/ngx_http_core_module.ht
On Thursday, 15 September 2016 at 13:26:48 UTC, Steven
Schveighoffer wrote:
On 9/15/16 9:11 AM, Chris wrote:
On Wednesday, 14 September 2016 at 20:23:09 UTC, Steven
Schveighoffer
wrote:
Hm.. I have adjusted this in my project, and it works (set to
50M).
Needed it for uploading large images
On 9/15/16 9:11 AM, Chris wrote:
On Wednesday, 14 September 2016 at 20:23:09 UTC, Steven Schveighoffer
wrote:
Hm.. I have adjusted this in my project, and it works (set to 50M).
Needed it for uploading large images.
Using version 0.7.29
-Steve
It doesn't seem to make any difference in my c
On Wednesday, 14 September 2016 at 20:23:09 UTC, Steven
Schveighoffer wrote:
Hm.. I have adjusted this in my project, and it works (set to
50M). Needed it for uploading large images.
Using version 0.7.29
-Steve
It doesn't seem to make any difference in my case. I wonder what
could be wr
On 9/14/16 9:58 AM, Chris wrote:
The vibe.d server rejects `XMLHttpRequest`s that are too long (in the
eyes of the server). In the docs it says
"maxRequestSize ulong
Maximum number of transferred bytes per request after which the
connection is closed with [sic!]"
However, when you go to
htt
The vibe.d server rejects `XMLHttpRequest`s that are too long (in
the eyes of the server). In the docs it says
"maxRequestSize ulong
Maximum number of transferred bytes per request after which the
connection is closed with [sic!]"
However, when you go to
http://vibed.org/api/vibe.http.ser
13 matches
Mail list logo
