Content
@
0 reply
0 recast
0 reaction
horsefacts
@horsefacts.eth
Handling all Frame redirects by returning 302s is a bit of a pain. We are considering simplifying the design. If you have feedback or suggestions on simplifying redirects, I'd love to hear them! One obvious addition is a simple "external link" button with no server round trip. What else could be better?
7 replies
2 recasts
38 reactions
vrypan |--o--|
@vrypan.eth
I still don't understand why the post_redirect does not happen in the browser, and you need an intermediate step. (Isn't there a browser equiv of curl -X POST?)
2 replies
0 recast
0 reaction
horsefacts
@horsefacts.eth
The biggest benefit is that the server can check for new data in the frame message and determine where to redirect. So if you want a dynamic redirect, use a 302, if you want a static redirect, we'll probably define a separate tag.
1 reply
0 recast
1 reaction
vrypan |--o--|
@vrypan.eth
My question is: Why should WC do the POST (in post_redirect) and not the browser directly? If the response is a 302 the browser will follow it. If it's a 200 it will show it. It's up to the server that receives the POST to decide what to do.
1 reply
0 recast
0 reaction
