fix: add CORS headers to LNURL and NIP-05 endpoints#5
Merged
Conversation
Browser-based Lightning wallets (PWAs) were unable to fetch the /.well-known/lnurlp/* and /.well-known/nostr.json endpoints due to missing CORS headers. LUD-01/LUD-16 and NIP-05 are explicitly designed to be consumed by browser clients, so these endpoints must allow cross-origin access. Add a withCORS middleware that sets Access-Control-Allow-Origin: * on every response and short-circuits OPTIONS preflight with 204. Closes #4
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.
withCORSmiddleware that setsAccess-Control-Allow-Origin: *,Access-Control-Allow-Methods: GET, OPTIONS, andAccess-Control-Allow-Headers: Content-Typeon every response from the public.well-knownendpoints./.well-known/lnurlp/{user},/.well-known/nostr.json, and/.well-known/lnurlp/{user}/callback.Closes #4