Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update 01.md
  • Loading branch information
shocknet-justin authored Jun 17, 2024
commit 59ba7da73719ca781bbfc85851b4212a4271d8d3
2 changes: 1 addition & 1 deletion 01.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ Neither status codes or any HTTP Header has any meaning. Servers may use whateve

## CORS Browser Compatibility

Application endpoints or Reverse Proxy directives that are accessed when using the LNURL must respond to `OPTIONS` requests on that endpoint. In their replies to `GET` and `OPTIONS`, they must set the header `Access-Control-Allow-Origin: *` for LNURL's to work with browser-based wallets, services and other webapps. If they set the `Access-Control-Allow-Methods` header, they must set in such a way that `GET` requests are permitted.
Application endpoints (or their defined Reverse Proxy directives) accessed when using the LNURL must respond to `GET` having set the header `Access-Control-Allow-Origin: *` for LNURL's to work with browser-based wallets, services and other webapps. If they set the `Access-Control-Allow-Methods` header, they must set in such a way that `GET` requests are permitted.

## Decoding examples

Expand Down