Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LUD-01: Recommendation to add CORS headers for all server responses #259

Open
adambor opened this issue May 12, 2024 · 1 comment
Open

Comments

@adambor
Copy link

adambor commented May 12, 2024

Some LNURL services are currently inaccessible from web apps (PWA wallets like Mutiny, swap services like boltz.exchange or atomiq.exchange) due to missing CORS (Cross-Origin Resource Sharing) header. I would suggest adding a recommendation to add a CORS header for all server response in the base LUD-01 spec, so that LNURLs can be accessed from web apps. It's important for the new and existing LNURL service implementations to understand the need for providing such a header to make their service work with customers using web app wallets or other apps that might have a need to access LNURL services from within the browser environment.

@kilrau
Copy link

kilrau commented May 13, 2024

💯

Whenever we had an issue with lnurl resolution in our web app, it was always CORS. Literally always.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants