fix: pass origin checking anyway in v0.13 #1411
Merged
Conversation
This file contains 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
Myriad-Dreamin
changed the title
Parsifa1
added a commit
to Parsifa1/typst-preview.nvim
that referenced
this pull request
Feb 26, 2025
|
Agree that should be fine. Normal browsers always send an |
chomosuke
pushed a commit
to chomosuke/typst-preview.nvim
that referenced
this pull request
Feb 28, 2025
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.
Make origin checking soft for a while for people using tools like typst-preview.nvim. They use a client that doesn't set
Origincorrectly. The check was introduced in #1157. Note: if you use a trusted and verified browser, the scripts inside still cannot bypass the origin checking.Example to eliminate the error in log (typst-preview.nvim)
The clients using websocat can set the origin to
http://localhost.CC @tmistele @chomosuke. Related issue: