-
Notifications
You must be signed in to change notification settings - Fork 13
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
Allow following redirects when requesting payment method ‘HEAD’ #28
Comments
@rsolomakhin my vague memory (possibly incorrect) of how we decided on this is that I asked you "should we follow redirects?" and you said "no" so we just put that into the spec. (I think maybe you put it into your original draft this document was based on.) Any thoughts? |
@domenic Rouslan is on leave until July. Since it's blocking a big implementer, I think we should do the reasonable thing and allow redirects? |
Which implementer are you referring to? In general I don't feel comfortable making changes on behalf of a single implementer, and would rather have a wider working group discussion. |
I'm also surprised that you would characterize this as blocking. The spec is still implementable in its current form, and if in the future we decide to expand it to allow redirects, that is a backward-compatible change. |
I think we are safe to leave this out of the spec until we have discussed it in the WG. Implementors are free to experiment with allowing redirects in the interim. |
Change 'redirect mode' to 'follow' in section '3.3. Fetching payment method manifests' algorithm 4.1.
Products, servers could change, so it looks reasonable to allow redirects. And it looks also safe to follow redirects since the owner controls the first url.
The text was updated successfully, but these errors were encountered: