Skip to content

Conversation

@taimoorzaeem
Copy link
Collaborator

BREAKING CHANGE

Closes #3391.

@taimoorzaeem taimoorzaeem marked this pull request as draft November 24, 2025 09:01
@taimoorzaeem
Copy link
Collaborator Author

taimoorzaeem commented Nov 24, 2025

This is an attempt to fix #3391. About 6 spec tests break because according to this fix (and even before it), they are a bug.

For the solution, I have added a */* mapping for each resolved media handler type. So, now it would work for both say Accept: text/javascript and Accept: */*. All other solutions that I tried were not as scalable and performant.

Looking for feedback on this.

@taimoorzaeem taimoorzaeem changed the title fix: content-type not set with custom domain and accept */* [WIP] fix: content-type not set with custom domain and accept */* Nov 24, 2025
@taimoorzaeem taimoorzaeem added the breaking change A bug fix or enhancement that would cause a breaking change label Nov 24, 2025
BREAKING CHANGE

Adds a `*/*` to available media type mapping. Now, the server
responds with available media type when `Accept: */*`.

Signed-off-by: Taimoor Zaeem <taimoorzaeem@gmail.com>
@taimoorzaeem taimoorzaeem changed the title [WIP] fix: content-type not set with custom domain and accept */* fix: content-type not set with custom domain and accept */* Nov 28, 2025
@taimoorzaeem taimoorzaeem marked this pull request as ready for review November 28, 2025 07:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking change A bug fix or enhancement that would cause a breaking change

Development

Successfully merging this pull request may close these issues.

Content-type not set when function returning a domain representing media type is requested with Accept "*/*" header

1 participant