I have Nginx sitting in front of a php5-fpm pool via fastcgi. The
application will serve static assets by means of responding with an
X-Accel-Redirect to an internal location.
My intention is to avoid repeatedly hitting the app for a particular URL for
short periods of time to cover bursts of traf
Jonathan Matthews Wrote:
---
> On 17 June 2014 07:49, gwilym wrote:
> > The workaround is to _double_ encode so as to send back
> > "image%2520with%2520spaces.jpg" to Nginx but we can't roll this out
> until
&g
We are updating Nginx from 1.4.7 and 1.6.0 and noticed an error in our app
likely related to the 1.5.9 change: now nginx expects escaped URIs in
"X-Accel-Redirect" headers.
We have an internal location for proxying content from a backend HTTP system
(Swift, actually). The location block looks like
