On Fri, Oct 05, 2018 at 08:59:21AM -0700, Brian W. wrote:
Hi there,
> In have this largely working aside from the above. If I proxy pass to the
> url with a # in it it's treated like a comment and ignores the rest. If I
> encode it with %23 I get a 404 error. What have you all done to get past
>
On Sat, Oct 06, 2018 at 05:15:50PM -0400, Denis Papathanasiou wrote:
Hi there,
> As noted here -- https://github.com/gin-gonic/gin/issues/1582 -- I have a
> simple web app that handles multipart form file uploads correctly on its
> own, but when I put it behind a simple proxy_pass configuration l
You need to understand what requests are being received, what responses are
being sent and the actual keys being used to write to your cache.
This means intelligent request logging, possibly use of redbot.org, and
examination of your cache. I used to use a script that someone had posted here
y
Here’s the issue in action [video]: https://d.pr/v/HmAiK0
I am using Nginx http caching extensively with the following cache key
proxy_cache_key "$scheme://$host$uri";
I know this is a cache issue because I can invalidate it with
proxy_cache_bypass $arg_nocache;
Here’s a video of tha
As noted here -- https://github.com/gin-gonic/gin/issues/1582 -- I have a
simple web app that handles multipart form file uploads correctly on its
own, but when I put it behind a simple proxy_pass configuration like below,
the underlying application sees a null value where the file form data was.