Thanks Maxim Dounin,
The trick worked.
I did something like the following:
server {
large_client_header_buffers 12 64;
...
error_page 494 =400 /400.json;
error_page 400 /400.json;
location = /400.json {
add_header Funky-Header1 'Funky Value' always;
root /etc/nginx/error-files/;
Hello!
On Tue, Jun 05, 2018 at 05:34:10AM -0400, prajos wrote:
> Hi there,
> I'm using nginx nginx version 1.12.0 as a reverse proxy to my application
> servers.
> I allow certain top level checks like header size and count to be done at
> nginx level.
>
> The server block looks like the follow
Hi there,
I'm using nginx nginx version 1.12.0 as a reverse proxy to my application
servers.
I allow certain top level checks like header size and count to be done at
nginx level.
The server block looks like the following:
server {
listen443 ssl default_server;
..
large_client_header
Hi
I got something like this
error_page 404 /stderror404.html;
location = /stderror400.html {
root /var/www/error;
content_by_lua_file /var/www/error/stderror400.lua;
internal;
allow all;
}
and the lua file has
ngx.say( "Your source ip address
Do those pages have access to the previous pages details ? Like for
example client_verify ?
Thanks
A
On 22 March 2017 at 21:52, B.R. via nginx wrote:
> RTFM? :o)
>
> https://nginx.org/en/docs/http/ngx_http_core_module.html#error_page
> ---
> *B. R.*
>
> On Tue, Mar 21, 2017 at 11:18 PM, Alex S
RTFM? :o)
https://nginx.org/en/docs/http/ngx_http_core_module.html#error_page
---
*B. R.*
On Tue, Mar 21, 2017 at 11:18 PM, Alex Samad wrote:
> Hi
>
> How would I added custom info to the error page.
>
> Say like for 400 if its a cert error, how can I add that to the page and
> maybe to add in
Hi
How would I added custom info to the error page.
Say like for 400 if its a cert error, how can I add that to the page and
maybe to add in the clients ip address as well
A
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listin
On Fri, Oct 02, 2015 at 07:30:28AM -0400, bjoe2k4 wrote:
Hi there,
> i was wondering if it is possible to have custom error pages *without* the
> error page locations inheriting the http or server level access_log
> directives.
Requests are logged in the context of a location where p
Hi,
i was wondering if it is possible to have custom error pages *without* the
error page locations inheriting the http or server level access_log
directives. Please consider the following config:
--
server {
listen *:80;
server_name test.domain;
root /app/www
Thanks!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,252825,252880#msg-252880
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Tue, Aug 26, 2014 at 08:41:31AM -0400, kay wrote:
> How can "if in location" influence productivity?
There is no difference from performance point of view.
--
Maxim Dounin
http://nginx.org/
___
nginx mailing list
nginx@nginx.org
http://mai
How can "if in location" influence productivity?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,252825,252844#msg-252844
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Tue, Aug 26, 2014 at 04:48:41AM -0400, kay wrote:
> It is not possible to set custom error page. For example
> /usr/share/nginx/404.html contains "test":
>
> server {
> error_page 404 /404.html;
>
> if ($request_method = "GET")
> return 404;
> }
>
> location / {
> proxy_pass http://
It is not possible to set custom error page. For example
/usr/share/nginx/404.html contains "test":
server {
error_page 404 /404.html;
if ($request_method = "GET")
return 404;
}
location / {
proxy_pass http://localhost:8080;
}
location /404.html {
/usr/share/nginx/404.html;
}
}
curl -v 127.0
14 matches
Mail list logo
