Thanks Zhang and Maxim!
I'm checking how to fix that on my backend.
Kind,
NM
2017-07-04 9:21 GMT-03:00 Maxim Dounin :
> Hello!
>
> On Mon, Jul 03, 2017 at 05:09:28PM -0300, Nelson Marcos wrote:
>
> > I don't know if it is an expected behaviour or a bug:
> >
&g
Hello everyone!
I don't know if it is an expected behaviour or a bug:
Scenario 1(OK): If I perform a request *with the header Range*, Nginx
serves the *partial content(HTTP 206)*.
Scenario 2 (NOT OK): If I perform a request *with the header Range AND the
header "If-Range" *with the Etag, Nginx
Thanks \o/
Um abraço,
NM
2017-03-17 14:46 GMT-03:00 Maxim Dounin :
> Hello!
>
> On Fri, Mar 17, 2017 at 02:21:55PM -0300, Nelson Marcos wrote:
>
> > Hello all,
> >
> > Right now we're using Nginx(as a proxy) to serve videos(4gb) and small
> > objects(
Hello all,
Right now we're using Nginx(as a proxy) to serve videos(4gb) and small
objects(< 100k), using Openstack Swift as backend.
Yesterday, I tried turn proxy_buffering off to see if it would improve
nginx performance but it didn't.
However, I realised that nginx stoped to write new files on
Do you really need to use different source ips or it's a solution that you
picked?
Also, is it a option to set the keepalive option in your upstream configure
section?
http://nginx.org/en/docs/http/ngx_http_upstream_module.html#keepalive
Um abraço,
NM
2017-03-07 16:50 GMT-03:00 larsg :
> Hi,
>
Hi Oliver!
How is your proxy_cache_key configured?
Um abraço,
NM
2017-02-24 9:33 GMT-03:00 0liver :
> We've recently started delivering image urls with query strings for
> cropping, like
>
> http://images-camping.info/CampsiteImages/116914_Large.
> jpg?width=453&height=302&mode=crop
>
> We've