fix(mcp): use request fetch for raw page content#1304
Merged
larbish merged 1 commit intonuxt-content:mainfrom Mar 12, 2026
Merged
fix(mcp): use request fetch for raw page content#1304larbish merged 1 commit intonuxt-content:mainfrom
larbish merged 1 commit intonuxt-content:mainfrom
Conversation
|
@onmax is attempting to deploy a commit to the NuxtLabs Team on Vercel. A member of the Team first needs to authorize it. |
commit: |
e6ea0b9 to
ef9f309
Compare
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.
Follow-up to #1302.
Summary
get-pagenow derives itsurlfrom the incoming request origin, which is correct for proxied and deployed environments. The remaining problem is that it still fetches its markdown body through an absolute self-request.That works locally, but on Cloudflare Workers the same-worker subrequest returns
404, solist-pagesworks whileget-pagefails withFailed to get page.This keeps the request-origin URL behavior but switches the content fetch to
event.$fetch('/raw${path}.md'), which resolves through Nitro's request-bound fetch path instead of an outbound absolute request. That preserves the existing raw markdown response shape and avoids reconstructing markdown from parsed content data.Reproduction
get-pagereturnsFailed to get pageget-pagereturns the raw markdown contentVerify
Broken worker:
Fixed worker:
Local source verification: