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.

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

[SEP24] Remove the 403 forbidden stuff from the interactive endpoint #455

Merged
merged 1 commit into from
Nov 22, 2019

Conversation

msfeldstein
Copy link
Contributor

One of the vestigial remains of the evolution of SEP6 is that the call to return the interactive URL should return as a 403 forbidden. This made sense when sep6 could be interactive or non-interactive and there were multiple ways to get through the flow, 403 was the closest thing to "More user info needed". Given that this is now the one and only happy path we should probably cut the cord on this 403 response, and just show it as the correct response.

It would be good to land this at the same time as #438 since its already a breaking change regarding these endpoints, we can do it all at once.

@istrau2
Copy link
Contributor

istrau2 commented Nov 14, 2019

To be clear, this would change on the new SEP24 endpoint. However on the proposed SEP26 endpoint, it would have to remain as 403, correct?

If so, I am a supporter.

@msfeldstein
Copy link
Contributor Author

msfeldstein commented Nov 14, 2019 via email

@msfeldstein
Copy link
Contributor Author

Sorry that is incorrect. The endpoints in sep26 that are 403 make sense as 403, so i will leave them.

@istrau2
Copy link
Contributor

istrau2 commented Nov 14, 2019

Yeah, agreed, on SEP26 I think it should remain as 403.

@istrau2
Copy link
Contributor

istrau2 commented Nov 14, 2019

hmm what about SEP24 withdawal? Doesn't that need a 403 response (because 200 means anchor has everything it needs)?

@msfeldstein
Copy link
Contributor Author

I feel like sep24 withdraw should always go through the interactive flow if for nothing else than to show the confirmation of exactly whats going to happen (exact fees, exact withdraw account details, etc). Those things are always so anchor specific im not sure its a good UX to just press withdraw then confirm

@istrau2
Copy link
Contributor

istrau2 commented Nov 20, 2019

+1 get rid of 403 entirely in the interactive workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants