w3c / payment-method-manifest

Specification for Web Payments payment method manifests
https://w3c.github.io/payment-method-manifest/
Other
9 stars 13 forks source link

Allow following redirects when requesting payment method ‘HEAD’ #28

Open gogerald opened 6 years ago

gogerald commented 6 years ago

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.

gogerald commented 6 years ago

@zkoch @domenic

domenic commented 6 years ago

@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?

gogerald commented 6 years ago

@madmath

madmath commented 6 years ago

@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?

domenic commented 6 years ago

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.

domenic commented 6 years ago

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.

adrianhopebailie commented 6 years ago

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.