Not sure if this is foolproof ... but maybe you can use the error_page
fallback by responding with a special status_code.
http://nginx.org/en/docs/http/ngx_http_core_module.html#error_page
location / {
proxy_pass http://validator;
error_page 510 = @success;
}
location @success {
pro
Hi ,
Please note that we are using nginx v 1.10.2 and on one of our webserver
(centos 7.2) we are observing below error and sudden stopping of nginx
service repeatedly at fix time i.e. at 2:00 am. Below are error lines for
your reference :
2017/02/26 02:00:01 [alert] 57550#57550: *131331605 open
Hello!
On Sun, Feb 26, 2017 at 01:08:02PM -0500, jeanpaul wrote:
> I stripped down my configuration and removed 'unneeded' parts to reproduce.
>
> I'm able to reproduce it with the following settings:
>
> location / {
> # Added to mitigate the issue. Removed for testing
> #rewrite
Hi Aleksandar,
Thank you , my requirement is i need LB to redirect to same OHS server
where i have multiple httpd server's running.
Regards
"" Anto Telvin Mathew ""
On Sat, Feb 25, 2017 at 4:29 AM, Aleksandar Lazic wrote:
> Hi Anto.
>
>
> Am 24-02-2017 19:03, schrieb Anto
Or is there any existing module that can be adapted to achieve this?
Appreciate if someone can shed some light. Thx,
- Alder
On Sat, Feb 25, 2017 at 9:24 PM, Alder Netw wrote:
> Hi I want to add an ICAP-like front-end validation server V with nginx.
> The user scenario is like this:
>
> The clie
Hi Maxim,
I stripped down my configuration and removed 'unneeded' parts to reproduce.
I'm able to reproduce it with the following settings:
location / {
# Added to mitigate the issue. Removed for testing
#rewrite ^/index.html$ / break;
proxy_pass http://backends;
proxy_
So in the documentation and from what I see online everyone is limiting
requests to prevent flooding on dynamic pages and video streams etc.
But when you visit a HTML page the HTML page loads up allot of various
different elements like .css .js .png .ico .jpg files.
To prevent those elements also
Hello!
On Sun, Feb 26, 2017 at 10:43:53AM +0100, Jean-Paul Hemelaar wrote:
> Hi all,
>
> I tested the new proxy_cache_background_update function to serve stale
> content while fetching an update in the background.
>
> I ran into the following issue:
> - PHP application running on www.example.co
Hi,
The proxy_cache_key uses request parameters by default. As stated in
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_key it
uses $scheme$proxy_host$request_uri by default.
The $request_uti do contain the request parameters:
http://nginx.org/en/docs/http/ngx_http_core_mod
Hi all,
I tested the new proxy_cache_background_update function to serve stale
content while fetching an update in the background.
I ran into the following issue:
- PHP application running on www.example.com
- Root document lives on /index.php
As soon as the cache has expired:
- A client request
10 matches
Mail list logo