I see, really thanks to your advice.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,281635,281642#msg-281642
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
> Wondering if there is a way to use the URL endpoint to check.
One way to do it would be with:
http://nginx.org/en/docs/http/ngx_http_auth_request_module.html
You said you have nginx+ which has the ability to reconfigure the the backends
on the fly: http://nginx.org/en/docs/http/ngx_http_upst
So i can see that I can do something like the maintenance mode example,
e.g.
if (-f $document_root/under_maintenance.html) {
return 503;
}
Wondering if there is a way to use the URL endpoint to check.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,281639,281640#msg-281640
___
Hi.
I'll try to make this make sense. I have a few web applications that I can't
change. They are behind an nginx+ loadbalancer. I have separate database
state that indicates whether or not requests should be forwarded to the
upstream, or a status page should be returned.
There is a web service t
I am setting up an nginx SMTP proxy and using XCLIENT to get the real
client info to the backend Postfix servers. I'm interested in also
using it for POP3 and IMAP to backend Dovecot servers - it looks like
Dovecot supports XCLIENT in POP3 and ID in IMAP to pass the same real
info. Is there any s
Hello!
On Thu, Oct 18, 2018 at 04:18:50PM +0200, garb...@gmx.de wrote:
> We are in the process of replacing a rather old web application. The old
> application used links that look like this:
>
> https://nameofapp/do?param1=A&id={ABC-DEF-GHI}¶m2=B
>
> I know that as far as RFC is concerned { a
We are in the process of replacing a rather old web application. The old
application used links that look like this:
https://nameofapp/do?param1=A&id={ABC-DEF-GHI}¶m2=B
I know that as far as RFC is concerned { and } are not valid characters but
unfortunately the application was built that way a
Hello!
On Thu, Oct 18, 2018 at 09:29:31AM -0400, kimown wrote:
> Hi, I want to log my entire request_body, but access.log contains some
> strange backslash, how can I remove these backslash before doube quote?
>
> Here is my nginx.conf,
> ```
> log_format main escape=json '$request_body';
>
>
Hi, I want to log my entire request_body, but access.log contains some
strange backslash, how can I remove these backslash before doube quote?
Here is my nginx.conf,
```
log_format main escape=json '$request_body';
access_log logs/access.log main;
```
This is my request code:
```
fetch('htt
Hello!
On Thu, Oct 18, 2018 at 08:12:00AM -0400, wld75 wrote:
> I have verified the nginx.conf and found no abnormality in logging section:
> please see below from the nginx.conf.
> i can see all requests for upload requests only in the access.log, but
> download request not appeared.
As previ
Hello,
Thanks for your support.
I have verified the nginx.conf and found no abnormality in logging section:
please see below from the nginx.conf.
i can see all requests for upload requests only in the access.log, but
download request not appeared.
##
# Logging Settings
11 matches
Mail list logo