search

lnurl / luds

lnurl specifications
603 stars 143 forks source link

Unspecified response status codes #214

Open brianoflondon opened 1 year ago

brianoflondon commented 1 year ago

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 commented 1 year ago

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.