http://join.pointtome.com
Jb Hobbs
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Does anyone know how I can debug this issue?
nginx (latest version and 1.9 too) running on iMac
Safari running on macbook
thunderbolt2 cable between the two of them.
Any download of https file from nginx downloads random start part of the
file then
Safari reports in red "The network connection wa
See, or please try:
http://jsfiddle.net/qe44nbwh/
If you see what I see in my IE11, when I press Start Test, and the target
is nginx.org, the duration for each request goes slow/normal/slow/normal
But when I change nginx.org to google.com, the timing is
normal/normal/normal ...
This only happens
A pointer on source modifications would be great.
In which function is the logical/best place to set custom socket options
after accept, from variable values set in nginx.conf, eg per location?
or, is it best to copy and modify an existing extension that uses that
hook. If so, which extension?
tha
At least in my experience unless your most used static files exceed in size
your available RAM, or are changing, they are effectively cached by the OS
anyway.
So storing them on a ram disk is really doing the same or worse job than
just letting the OS store them and serve them from its file cache
thanks,
the part where you massage the content lengths I was missing -- or had no
clue would be needed.
On Sat, Apr 18, 2015 at 12:06 PM, Valentin V. Bartenev
wrote:
> On Saturday 18 April 2015 11:23:54 jb wrote:
> > gotcha, I saw the discarded body thing in the debug log. ok thank
thanks
On Sat, Apr 18, 2015 at 11:23 AM, jb wrote:
> gotcha, I saw the discarded body thing in the debug log. ok thanks,
> um, how do you proxy_pass to nginx itself ?
>
> can you give an example ?
> just proxy_pass http://127.0.0.1/
> and proxy_pass_request_body off
at, Apr 18, 2015 at 11:10 AM, Valentin V. Bartenev
wrote:
> On Saturday 18 April 2015 10:24:17 jb wrote:
> > And maybe I am approaching this the wrong way? can you comment..
> >
> > I want an nginx upload target for POST that reads the content, discards
> it,
> > and repo
server?
thanks.
On Sat, Apr 18, 2015 at 10:08 AM, jb wrote:
> thanks and this is a popular answer on stack exchange but no, it does not
> work, because aborted requests have read less bytes -- $request_length
> reports how many bytes SHOULD have been read, but in the case of any
>
..
For accounting purposes, I'd want an exact mirror to $bytes_sent ...
otherwise math does not add up :( I think there should be a $bytes_recd ..
On Sat, Apr 18, 2015 at 9:47 AM, Valentin V. Bartenev
wrote:
> On Saturday 18 April 2015 08:23:37 jb wrote:
> > Is there a variable
Is there a variable for bytes read ?
$content_length is what should be read, but if the request is terminated
early, it is wrong.
$request_length is not right either, it is logging 459 bytes on a 9mb
upload.
thanks
___
nginx mailing list
nginx@nginx.org
It is true that the best way to rate limit is the sender. But in the event
where the sender is a myriad different browsers, that isn't an option.
There is no control at the POST level to throttle an upload. There isn't
really any good firewall tool for traffic shaping incoming data per tcp
stream e
Anyone? no ideas?
how would i go about getting such a feature added. I imagine it would be
much the same code, just applied to reading the request body rather than
writing it. And since it is core functionality I'm not sure one for POST
should be an extension?
On Wed, Apr 8, 2015 at 4:23 P
Is there a module that does throttled reading for POST and works the same
way as limit_rate does for GET (per stream, X bytes per second).
I got some kind of throttle effect by putting a usleep() into the
os/unix/ngx_recv.c file reader, but I want to use something that works the
same way as limit_
14 matches
Mail list logo