-
Notifications
You must be signed in to change notification settings - Fork 142
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
Unspecified response in case of invalid request #6
Comments
Currently the only client implementation (BLW) awaits for a valid Json as a response there and shows a raw error dump if anything goes wrong (Json could not be parsed, non-200 status code etc). Perhaps we can use a scheme similar to .6 there ( |
I've updated both BLW and spec according to my above proposal for now. |
The error handling wasn't specified before. Now the specification updated to include it, so this code was changed accordingly. See lnurl/luds#6
Yeah, that works for me well. I've updated lnch-vekslak. |
The specification doesn't describe what response should be at step 2 when there's an error - e.g. the secret is invalid. Should there be specific JSON body or just HTTP error? Which HTTP error?
The text was updated successfully, but these errors were encountered: