gzip disrupts users?

2015-09-03 Thread Grant
Over the years, whenever I've enabled gzip compression on my web server I've seen website conversions drop. I just enabled compression on nginx again and I noticed conversions drop again: gzip on; gzip_disable msie6; gzip_types application/javascript text/css; Any thoughts on this? Is there mor

Re: How to edit url and pass forward to wsgi?

2015-09-03 Thread Francis Daly
On Thu, Sep 03, 2015 at 08:40:36AM -0400, Thomas Nyberg wrote: Hi there, > On a related note, is there some way to log the location choices > that are made? I tried using a debug logging mode, but it was far > too low-level (on the level of memory allocations). Of course I > could have the routes

logging access in stream module

2015-09-03 Thread mex
hi, is there a way to log access (ip, date, size of payload) within the stream-module? i found error - log configurable for the stream only so far. cheers, mex Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261411,261411#msg-261411 ___

Re: nginx v1.8.0 / redirects

2015-09-03 Thread fsantiago
I hear what you're saying. i will do that instead and test it out. thank you. -- Fabian S. On 2015-09-02 03:02, B.R. wrote: > I would suggest you avoid multiple redirects in the case a client connects > with http://domain [1], because your current setup will make the client > following t

Re: How to edit url and pass forward to wsgi?

2015-09-03 Thread Thomas Nyberg
Thank you very much for the response. It's working now. I didn't realize that the regular expressions needed anchoring. I'm used to regular expressions where '.*' is needed for the functionality you refer to. On a related note, is there some way to log the location choices that are made? I tri

Re: How to edit url and pass forward to wsgi?

2015-09-03 Thread Francis Daly
On Thu, Sep 03, 2015 at 12:44:09AM -0400, Thomas Nyberg wrote: Hi there, > location ~ /staging/dog/.*/info/cat { "~" means "regex match". You haven't anchored the regex, so a request for /staging/dog/x/info/cat will match this, but so will a request for /a/staging/dog/x/info/cat/b > direct

Re: Implementing proxy_cache_lock when updating items

2015-09-03 Thread footplus
Thanks for your reply. I'm currently using this mechanism (small variation of yours) to work around the limitation. On every intermediate cache server, i'm using the following (whole chain is using nginx). map $upstream_cache_status $accel_expires_from_upstream_cache_status {