Thanks
I am not sure why we don't first compress and then store the same in the
cache. In this way, we don't have to compress the content each time (if the
client is asking for a gzipped content) before sending to client.
I am not able to understand why it is currently designed thisway,
Post
Thanks Patrick, I meant weak etags, happy to see them on 1.7.3!
On Mon, Sep 1, 2014 at 9:24 AM, Patrick Laimbock
wrote:
> On 01-09-14 14:18, Reinis Rozitis wrote:
>
>> is there is roadmap for ETags? I really miss that on nginx...
>>>
>>
>> What do you mean by that?
>>
>> http://nginx.org/en/doc
On 01-09-14 14:18, Reinis Rozitis wrote:
is there is roadmap for ETags? I really miss that on nginx...
What do you mean by that?
http://nginx.org/en/docs/http/ngx_http_core_module.html#etag on by
default since 1.3.3.
And from http://nginx.org/en/CHANGES
Changes with nginx 1.7.3
is there is roadmap for ETags? I really miss that on nginx...
What do you mean by that?
http://nginx.org/en/docs/http/ngx_http_core_module.html#etag on by default
since 1.3.3.
rr
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/ma
Maxim, is there is roadmap for ETags? I really miss that on nginx...
On Mon, Sep 1, 2014 at 6:41 AM, Maxim Dounin wrote:
> Hello!
>
> On Mon, Sep 01, 2014 at 03:20:23AM -0400, nginxsantos wrote:
>
> > Any thoughts on this?
>
> As you already found out, nginx stores responses as got from the
> b
Hello!
On Mon, Sep 01, 2014 at 03:20:23AM -0400, nginxsantos wrote:
> Any thoughts on this?
As you already found out, nginx stores responses as got from the
backend server. If you want to store compressed responses - they
have to be returned compressed by the upstream. If your upstream
serv
Any thoughts on this?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,252885,252979#msg-252979
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
How can use these two together. Suppose I got an uncompressed response from
the backend/webserver. I want Nginx to compress the response before storing
in the cache. Looks like Nginx is first storing the response in the cache
and then doing a compression before sending the response to the client.
H
