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.

Sign up for GitHub

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

Jump to bottom

Unspecified response status codes #214

Open
brianoflondon opened this issue Apr 16, 2023 · 1 comment
Open

Unspecified response status codes #214

brianoflondon opened this issue Apr 16, 2023 · 1 comment

Comments

@brianoflondon
Copy link

brianoflondon commented Apr 16, 2023 •
edited
Loading

As far as I can see this spec doesn't specify response status codes.

For example most LNURLp implementations I've come across return 200 after the call to /.well-known/lnurp/something.

I just found that this one from IBEX:

LNURL1DP68GURN8GHJ76TZV4UXSATZ9E5KYETCD4JHYCMPV3HJUCM0D5HKCMN4WFKZ7URP0YHKJMNKDA5KXEFDWFJHZATFWFJK6ETWW3EN76E385CKGCTRXCENGDPEXQURGCF5XSERWE3KVYMRXWF3VEJRWCMPVESNGVFKXY6XYCMPX4JNZD3NVCUNXDRX8P3K2ER9VCCRVVP5XGCRJEF3E60P6U

Returns 201. Understandable but there should be a clear spec.
@hsjoberg
Copy link
Collaborator

The spec is clear on this.
The basis of LNURL (LUD-01) says that HTTP codes have no meaning.

Neither status codes or any HTTP Header has any meaning. Servers may use whatever they want. Clients should ignore them

Any client would know how to handle errors anyway because a JSON object with an error should get received.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hsjoberg @brianoflondon