Re: Same cached objects, but different body_bytes_sent

2017-06-08 Thread Guilherme
Thanks for your response, Zhang. I included content-length in log_format to see: y.y.y.y - [08/Jun/2017:22:15:46 +] "GET /image.jpg HTTP/2.0" 200 466 HIT "Mozilla/5.0 (Linux; Android 5.0.1; GT-I9515L Build/LRX22C) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.83 Mobile Safari/537.36

Re: upstream 429 and non-idempotent request

2017-06-08 Thread Frank Liu
I fully understand the rationale of not retrying non-idempotent requests if they are already sent, but in case of 429 (maybe other cases as well), I don't see an issue of retrying even if request is sent. It would be better if we can selectively do something like "proxy_next_upstream non-idempotent

2017 NGINX User Survey: Help Us Shape the Future

2017-06-08 Thread Owen Garrett
It’s that time of year for the annual NGINX User Survey. We're always eager to hear about your experiences to help us evolve, improve and shape our product roadmap. Please take ten minutes to share your thoughts: http://survey.newkind.com/r/rSzd0p89/ Th

Re: upstream 429 and non-idempotent request

2017-06-08 Thread Maxim Dounin
Hello! On Thu, Jun 08, 2017 at 01:10:25AM -0700, Frank Liu wrote: > In case of upstream returning 429, I'd like to have nginx retry next > upstream server. Since nginx by default won't retry non-idempotent > requests, how do I force nginx to retry when receiving 429? I imagine this > should be th

Re: back-reference from if() and rewrite?

2017-06-08 Thread Ingo Lafrenz
Hi, Let me give you a couple of hints (esp when you come from Apache): - stop thinking like you have apache. nginx and apache are fundamentally different when it comes to rewriting - nginx rewrites only consider the location part of the URL during matching, so whenever you need to do work based

upstream 429 and non-idempotent request

2017-06-08 Thread Frank Liu
In case of upstream returning 429, I'd like to have nginx retry next upstream server. Since nginx by default won't retry non-idempotent requests, how do I force nginx to retry when receiving 429? I imagine this should be the default behavior anyway, or does nginx not care about returning code and w

Re: Nginx rule for subdomains: ERR_TOO_MANY_REDIRECTS

2017-06-08 Thread iivan
Hi Igal, Firstly, thank you for your answer. I also like to find you on this forum (I am a lucee user :) ), Can you give me a tip how to do it? Here's the full configuration file: https://gist.github.com/ivanionut/946468ce86086a55937e92c7249e3ed7 It was working correctly before the upgrade to th