fix: set correct Content-Type for opensearch.xml#115
Merged
danielroe merged 1 commit intonpmx-dev:mainfrom Jan 26, 2026
Merged
Conversation
Set Content-Type to application/opensearchdescription+xml to prevent Vercel from injecting preview toolbar scripts into the XML response.
|
@BYK is attempting to deploy a commit to the danielroe Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Member
|
thank you! and sorry, it was my mistake! |
vinnymac
pushed a commit
to vinnymac/npmx.dev
that referenced
this pull request
Jan 28, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Set the correct
Content-Typeheader for the OpenSearch XML response to prevent Vercel from injecting preview toolbar scripts.Follow up to #113.
Problem
Vercel's preview toolbar only injects scripts into responses with
Content-Type: text/html. Without an explicit Content-Type, the XML response was being treated as HTML, causing:Solution
Add
setHeader(event, 'Content-Type', 'application/opensearchdescription+xml')to the server route handler.