-
Notifications
You must be signed in to change notification settings - Fork 624
cloud_storage_clients
: check Content-Type
header before parsing REST error responses in s3_client
#25738
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
WillemKauf
merged 8 commits into
redpanda-data:dev
from
WillemKauf:s3_content_type_parse
Apr 15, 2025
Merged
cloud_storage_clients
: check Content-Type
header before parsing REST error responses in s3_client
#25738
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
7477d92
`http`: add `utils.cc/.h` and `flexible_function_handler`
WillemKauf 0f6d14a
`cloud_io`: use `flexible_function_handler` in `s3_imposter`
WillemKauf 8dd0922
`http`: use `flexible_function_handler` in `http_imposter`
WillemKauf a803a63
`http`: add new overload for `add_mapping::add_mapping_when::then_rep…
WillemKauf 115bf81
`cloud_storage`: set proper `Content-Type` header in `anomalies_detec…
WillemKauf 366027f
`cloud_storage_clients`: use `flexible_function_handler` in `s3_clien…
WillemKauf cc5b49f
`cloud_storage_clients`: move `get_response_content_type()` to `util`
WillemKauf 1cc76c7
`cloud_storage_clients`: parse `Content-Type` in `s3_client`
WillemKauf File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shall we dump few bytes of the response at trace log level to aid debugging in the future if we fall into this unexpected branch with non-xml/non-empty response?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah that would be a good idea, I can add it in a follow up