-
Notifications
You must be signed in to change notification settings - Fork 49
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
Cancel a IRMA session #140
Comments
I was not aware of this pattern, and agree that the current behavior is not optimal. So this is indeed open for improvement, thanks for pointing it out. If you'd like to submit a PR fixing it I would be happy to merge it 🙂 Otherwise we will fix this ourselves later. |
I'm a bit rusty on my I assume returning a |
I see there are no tests to check the HTTP status code, would you be open to help or write those specs? It seems to change the HTTP status code is pretty straightforward. I'll create a draft PR for this. |
Whenever you cancel an IRMA session (by sending DELETE
/session/[:token]
to the IRMA server), you get a200
response with an empty body (""
) from the server.A common design pattern for DELETE response is to either (1) use the
204
HTTP status code with an empty body (""
) or (2) a200
HTTP status code with the deleted session status as response ({ token: [token], status: "CANCELLED" }
).The current implementation mixes both design patterns, which leads to (IMO) an unexpected response for cancelling/deleting an IRMA session.
I was wondering; is this design on purpose, or is it open to improvement?
The text was updated successfully, but these errors were encountered: