fix: route ai search endpoint through the /developers proxy#637
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
The search dialog fetches the retriever endpoint as an origin-relative path derived from
basePath(/api/search). Users browse the docs behind thetempo.xyz/developersproxy, so the request resolved against tempo.xyz's root and hit tempo-web's trailing-slash 308 instead of the docs app.Production builds now set the endpoint to
https://tempo.xyz/developers/api/search, which the existing/developers/*proxy already forwards to the docs app (verified live with a202from the index warm-up). Previews and local dev keep the default relative endpoint since they are browsed on the app's own origin.Production needs a redeploy after merge to pick up the new endpoint.