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
"Too big request header" #238
Comments
Could you please provide an example (e.g., a curl command) to reproduce the error? |
I think this is related: traefik/traefik#8846 Maybe we can configure thr max header bytes for the error pages server aswell? Via a env variable or so. I dont really have an example on hand since i dont want to provide my auth cookies (for obvious reasons). |
I forked the project and introduced a new environment variable |
Very nice thank you! 😀 |
🚀 v2.26.0 |
I have this error with traefik.
My env
How to fix it ? Thank bro. |
Just increase the number until it works. A larger read buffer has only one negative side-effect: the resource consumption is slightly higher. On an average server and normal load conditions this should not cause any problems since error-pages does not require many resources in the first place. But it might make it easier for someone with bad intentions to deliberately overload your server by sending many requests with a lot of payload data. So you also don't want to increase the read buffer to the maximum possible value. |
Is there an existing issue for this?
Describe the bug
When the auth cookies for my website are present and I try to a non existing page I get "Too big request header" instead of the error page. When I clear said cookies I see my error page as expected.
Steps to reproduce
Configuration files
No response
Relevant log output
No response
Anything else?
I am not sure if this is a traefik issue, It does only happen with the error page container, accessing the normal webpage is fine with and without the auth cookies set.
The text was updated successfully, but these errors were encountered: