Skip to content
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

Return 431 status when headers are too large #45

Open
bpbecker opened this issue Apr 24, 2023 · 1 comment
Open

Return 431 status when headers are too large #45

bpbecker opened this issue Apr 24, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@bpbecker
Copy link
Contributor

When a request's headers exceed BufferSize we currently handle it as a DRC.Wait error and close the connection. I believe the more proper way to handle it is to issue a HTTP 431. This will give the client more information on how to correct the request.

431 Request Header Fields Too Large

The server is unwilling to process the request because its header fields are too large. The request may be resubmitted after reducing the size of the request header fields.
@bpbecker bpbecker added the enhancement New feature or request label Apr 24, 2023
@bpbecker bpbecker self-assigned this Apr 24, 2023
@bpbecker
Copy link
Contributor Author

This will require a change to Conga

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant