New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug?] Custom 404 page returns 200 OK header #275
Comments
Fixed by #315 |
What about url /some_no_exist_url ? if nginx not rewrite to /404, it will return 200 ok (and will show 404.htm) (sory for my english) |
That's exactly what my PR fixed. Probably this fix is not in the current build, but it has been merged so it should be in one of the next builds. If you want to try it now you can just merge the change yourself locally. |
Yes, thank You! it's my mistake, really 404 :) |
If you set your own
404.htm
then navigate to a none existent URL, the header returns200 OK
instead of404 not found
, yet the default 404 page does return the correct 404 header ?Thanks to D503 over on the forum for pointing this out :)
The text was updated successfully, but these errors were encountered: