No, the 404 works as expected, the 413 does not.
I’ll try building from source some time early next week to see if that fixes
things.
-Dan
Sent from my iPhone
> On Oct 20, 2022, at 7:49 PM, Sergey A. Osokin wrote:
>
> On Thu, Oct 20, 2022 at 04:25:33PM -0400, Dan G. Switzer, II wrote:
>>
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.
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
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_
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
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;
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
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
