hotfix: serve /llms-full.txt as direct 200, not 307 - #603
Merged
Conversation
The route was redirecting to /api/llm-context, which is fine for permissive clients but breaks: - llms.txt validators (llmstxt-checker fails on non-200) - stricter AI crawlers (Perplexity, some Bing AI variants) that mark non-standard paths returning a redirect as no-content and skip - canonical attribution (AI engines citing the body now point at the internal /api/llm-context path instead of the public /llms-full.txt) Re-exports the GET handler from /api/llm-context so there is a single source of truth for the markdown body. No content change.
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
1 participant
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.
Cherry-pick of #602. Single-file change in /llms-full.txt route. Removes the 307 redirect that broke llms.txt validators and stricter AI crawlers.