On Mon, Jul 10, 2023 at 06:27:04AM +0200, Sten Grüner wrote:
Hi there,
> Got to do rewrites, since otherwise nginx breaks urlencoded query
> parameters.
Yes, that sounds like a good reason to not just use "the obvious" config.
So -- following the example in the trac ticket that you linked,
Hi Francis,Got to do rewrites, since otherwise nginx breaks urlencoded query parameters.nginx proxy_pass and URL decodingstackoverflow.comBRAm 10.07.2023 um 01:09 schrieb Francis Daly :On Fri, Jun 30, 2023 at 11:29:21AM +0200, Sten Gruener wrote:Hi there,I trying to mix authentication for POST req
On Fri, Jun 30, 2023 at 11:29:21AM +0200, Sten Gruener wrote:
Hi there,
> I trying to mix authentication for POST requests with some
> rewrite/proxy_pass logic. This mean that password is required only on
> POST/PUT requests.
This does not answer the question you asked, but is there a reason for
Dear all,
I trying to mix authentication for POST requests with some
rewrite/proxy_pass logic. This mean that password is required only on
POST/PUT requests.
location /x/ {
limit_except GET OPTIONS {
auth_basic "Write Access";
auth_basic_user_fi
Nader Ziada
Sent: Wednesday, October 18, 2017 18:55
To: nginx@nginx.org
Subject: workaround to handle HTTP and HTTPS on same port?
Hi,
In order to support HTTP and HTTPS on the same port we had to enable SSL for
that listen port in the nginx config and remap the 497 nginx error code to a
t_uri;".
This seems to work for the GET requests, but not for PUT requests.
This is a temporary workaround that we need while the more permanent
solution is being worked on, so we're wondering if anybody here had any
workarounds or tips on how to achieve that.
This workaround seems to do the trick for the time being:
if ($request_method = HEAD) {
add_header Content-Length 0;
add_header Content-Type text/plain
Hello!
On Wed, Jul 02, 2014 at 02:37:17PM +0400, Maxim Dounin wrote:
> Hello!
>
> On Tue, Jul 01, 2014 at 05:58:33PM +, Eric Swenson wrote:
>
> > On 6/22/14, 7:32 AM, "Maxim Dounin" wrote:
> >
> > >If there is nothing in error logs, and you are getting 502 errors,
> > >then there are two
Hello!
On Tue, Jul 01, 2014 at 05:58:33PM +, Eric Swenson wrote:
> On 6/22/14, 7:32 AM, "Maxim Dounin" wrote:
>
> >If there is nothing in error logs, and you are getting 502 errors,
> >then there are two options:
> >
> >1. The 502 errors are returned by your backend, not generated by
> >
Hello Maxim,
On 6/22/14, 7:32 AM, "Maxim Dounin" wrote:
>If there is nothing in error logs, and you are getting 502 errors,
>then there are two options:
>
>1. The 502 errors are returned by your backend, not generated by
> nginx.
>
>2. You did something wrong while configuring error logs and/
Hello!
On Fri, Jun 20, 2014 at 11:29:39PM +, Eric Swenson wrote:
> Hello Maxim,
>
> On 6/20/14, 3:46 PM, "Maxim Dounin" wrote:
>
> >Hello!
> >
> >On Fri, Jun 20, 2014 at 07:32:36PM +, Eric Swenson wrote:
> >
> >[...]
> >
> >> This works fine. However, every once in a while (say, every
Hello Maxim,
On 6/20/14, 3:46 PM, "Maxim Dounin" wrote:
>Hello!
>
>On Fri, Jun 20, 2014 at 07:32:36PM +, Eric Swenson wrote:
>
>[...]
>
>> This works fine. However, every once in a while (say, every
>> week or so), traffic to https://app.example.com/svc/api/
>> returns gateway 502 error
Hello!
On Fri, Jun 20, 2014 at 07:32:36PM +, Eric Swenson wrote:
[...]
> This works fine. However, every once in a while (say, every
> week or so), traffic to https://app.example.com/svc/api/
> returns gateway 502 errors. The API service (located at
> https://svc.example.com/api) is
We run a API web service and have two web sites that access the web service via
AJAX. The web sites are accessed via HTTPS and, for security reasons, we need
to have the API web service also accessed by HTTPS. Due to the need to support
the IE9 browser, which does not properly support CORS, we
Hello,
has anyone considered this simple workaround for BREACH and
gzip-compression, i.e. randomly interspersed flush()-es during compression?
https://github.com/wnyc/breach_buster
It would be compatible with all clients, and should be fairly easy to
implement in nginx (for nginx hackers).
Of
15 matches
Mail list logo
