[GH-ISSUE #1500] How to fix http response status 431 error? #326

New issue

Closed

opened 2026-03-07 20:47:46 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 20:47:46 +03:00

Owner

Originally created by @owenJiao on GitHub (Feb 24, 2023).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/1500

Dear Teams:
When I accessed cloudbeaver which was deployed in AKS, Web browser threw 431 error, the detail error message is "Bad Message 431, reason : Request Header Fields Too Large". The server side log of cloudbeaver is "org.eclipse.jetty.http.HttpParser - Header is too large 8193>8192". I haven't found any parameters that can enlarge the size of http header. So could you provide some tips to fix this error?
Thanks very much.

Originally created by @owenJiao on GitHub (Feb 24, 2023). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/1500 Dear Teams: When I accessed cloudbeaver which was deployed in AKS, Web browser threw 431 error, the detail error message is "Bad Message 431, reason : Request Header Fields Too Large". The server side log of cloudbeaver is "org.eclipse.jetty.http.HttpParser - Header is too large 8193>8192". I haven't found any parameters that can enlarge the size of http header. So could you provide some tips to fix this error? Thanks very much.

kerem closed this issue

2026-03-07 20:47:46 +03:00

kerem commented

2026-03-07 20:47:47 +03:00

Author

Owner

@dariamarutkina commented on GitHub (Mar 2, 2023):

Hello @owenJiao,
Please can you try clearing cookies, if that doesn't help, could you send Logs and a full Header, please?
Thank you for your interest in CloudBeaver.

@dariamarutkina commented on GitHub (Mar 2, 2023): Hello @owenJiao, Please can you try clearing cookies, if that doesn't help, could you send Logs and a full Header, please? Thank you for your interest in CloudBeaver.

kerem commented

2026-03-07 20:47:47 +03:00

Author

Owner

@TatyanaSsau commented on GitHub (Apr 4, 2023):

There is no updates for a long time.
@owenJiao please, feel free to contact me to reopen the ticket if it's still actual.

@TatyanaSsau commented on GitHub (Apr 4, 2023): There is no updates for a long time. @owenJiao please, feel free to contact me to reopen the ticket if it's still actual.