Re: Custom 413 error pages when client_max_body_size exceeded

2022-10-20 Thread Sergey A. Osokin
On Thu, Oct 20, 2022 at 04:25:33PM -0400, Dan G. Switzer, II wrote: > Sorry, that was a typo from the tweak to the real file names. The file > extensions matched in my test and I got the custom 404 error page. Dan, follow that everything works fine, could you confirm. Thank you. -- Sergey A.

Re: nginx-1.23.2

2022-10-20 Thread A. Schulze via nginx
Am 20.10.22 um 22:30 schrieb Maxim Dounin: Now for automatic ticket keys rotation it is enough to configure "ssl_session_cache shared:...", something you likely already have configured anyway. Everything else will be done by nginx: it will rotate keys every ssl_session_timeout. so it's enou

Re: nginx-1.23.2

2022-10-20 Thread Maxim Dounin
Hello! On Thu, Oct 20, 2022 at 09:45:17PM +0200, A. Schulze via nginx wrote: > > > Am 19.10.22 um 14:10 schrieb Maxim Dounin: > > Changes with nginx 1.23.219 Oct 2022 > > *) Feature: TLS session tickets encryption keys are now automatically > >

Re: Custom 413 error pages when client_max_body_size exceeded

2022-10-20 Thread Dan G. Switzer, II
Sorry, that was a typo from the tweak to the real file names. The file extensions matched in my test and I got the custom 404 error page. On 10/20/2022 4:22 PM, Frank Swasey wrote: You do realize you redirected to .htm and specified .html in the location, right? On Thu, Oct 20, 2022 at 14:0

Re: Custom 413 error pages when client_max_body_size exceeded

2022-10-20 Thread Frank Swasey
You do realize you redirected to .htm and specified .html in the location, right? On Thu, Oct 20, 2022 at 14:02 Dan G. Switzer, II wrote: > Sergey, > > Thanks for taking the time to respond. That's not working for me. I tried > the following: > > > server { > listen 80; > > client_max_

Re: nginx-1.23.2

2022-10-20 Thread A. Schulze via nginx
Am 19.10.22 um 14:10 schrieb Maxim Dounin: Changes with nginx 1.23.219 Oct 2022 *) Feature: TLS session tickets encryption keys are now automatically rotated when using shared memory in the "ssl_session_cache" directive. Hello, th

Re: Custom 413 error pages when client_max_body_size exceeded

2022-10-20 Thread Sergey A. Osokin
On Thu, Oct 20, 2022 at 02:01:44PM -0400, Dan G. Switzer, II wrote: > Thanks for taking the time to respond. That's not working for me. I > tried the following: [...] > The 404 works fine, but sending more than 10k to the request still > returns the default nginx page. [...] > Is there a good

Re: Custom 413 error pages when client_max_body_size exceeded

2022-10-20 Thread Dan G. Switzer, II
Sergey, Thanks for taking the time to respond. That's not working for me. I tried the following: server {     listen 80;     client_max_body_size 10k;     error_page 403 =404 /404_status_code.htm;     error_page 404 =404 /404_status_code.htm;     error_page 413 =413 /413_status_code.htm;   

Re: Custom 413 error pages when client_max_body_size exceeded

2022-10-20 Thread Sergey A. Osokin
Hi Dan, thanks for the report. On Thu, Oct 20, 2022 at 09:04:31AM -0400, Dan G. Switzer, II wrote: > I'm using nginx/1.20.1 under CentOS Linux release 7.9.2009 (Core) and I > cannot get a custom error page to show when the client_max_body_size > limit has been exceeded. The browser will only re

Custom 413 error pages when client_max_body_size exceeded

2022-10-20 Thread Dan G. Switzer, II
I'm using nginx/1.20.1 under CentOS Linux release 7.9.2009 (Core) and I cannot get a custom error page to show when the client_max_body_size limit has been exceeded. The browser will only return the default nginx error page. I see a number of posts mentioning how there was a bug in earlier ve