Skip to content

Handle streaming exceptions as bad requests instead of internal errors #178

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

Merged

Conversation

thinaih
Copy link
Member

@thinaih thinaih commented Mar 11, 2025

Currently the proxy handles most streaming issues due to mismatch between declared content length and uploaded content length as INTERNAL_ERRORs, except for when it's a STANDARD or W3C_CHUNKED and uploaded > content length, then this is handled as UNAUTHORIZED.

This PR is suggesting handle all of the above as BAD_REQUEST.

@cla-bot cla-bot bot added the cla-signed label Mar 11, 2025
@thinaih thinaih force-pushed the handle-stream-errors-as-client-errors branch from 0eb1106 to d7b16a8 Compare March 12, 2025 16:20
@thinaih thinaih marked this pull request as ready for review March 12, 2025 16:39
@thinaih thinaih requested a review from Randgalt March 24, 2025 13:20
Copy link
Contributor

@mosiac1 mosiac1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please squash the commits into a single one

@thinaih thinaih force-pushed the handle-stream-errors-as-client-errors branch from 6f8c32f to 9b0c4ab Compare March 25, 2025 09:55
@thinaih thinaih requested a review from mosiac1 March 25, 2025 10:00
@mosiac1
Copy link
Contributor

mosiac1 commented Mar 25, 2025

@Randgalt could you re-review please?

@mosiac1 mosiac1 merged commit 2b5f030 into trinodb:main Apr 1, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants