Skip to content

http: add xml support to http::mime_types::mappings #187

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

Open
wants to merge 1 commit into
base: v25.2.x-pre
Choose a base branch
from

Conversation

WillemKauf
Copy link

@WillemKauf WillemKauf commented Apr 7, 2025

It seems strange that xml isn't supported as a mime type here. We expect all S3 REST error responses to be returned with a Content-Type header of application/xml, so being able to map the extension here makes life a lot easier for testing with imposter http S3 servers/services.

Motivated by having to fix tests for redpanda-data/redpanda#25738.

It seems strange that `xml` isn't supported as a `mime` type here.
We expect all S3 REST error responses to be returned with a `Content-Type`
header of `application/xml`, so being able to map the extension here
makes life a lot easier for testing with imposter `http` S3 servers/services.
@WillemKauf WillemKauf requested review from dotnwat and rockwotj April 7, 2025 18:10
Copy link

@rockwotj rockwotj left a comment

Choose a reason for hiding this comment

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

Let's make sure to upstream (if you haven't already) too. LGTM

@WillemKauf
Copy link
Author

Let's make sure to upstream (if you haven't already) too. LGTM

Opened scylladb#2725

@WillemKauf
Copy link
Author

My upstream PR sparked good discussion on the seastar side of things, so we now have a better patch on the way: scylladb@c7e79b8

@travisdowns
Copy link
Member

My upstream PR sparked good discussion on the seastar side of things, so we now have a better patch on the way: scylladb@c7e79b8

Yes, this is common: my feeling is that unless (wall clock) time is really at a premium it's better to upstream first, then downstream the commits (optionally), as it leads to less overall churn.

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

Successfully merging this pull request may close these issues.

3 participants