You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If "Servers must not locate the actual change password page at the change password url" I would expect servers redirect to the actual change password page as a response. However "Clients must handle ok status responses", how would such response should be handled? I guess it should be handled anyway as a valid response, would be great to clarify.
I was wondering about this too, is this only for http-equiv=refresh? If they need to handle that, presumably they need to handle the Refresh header too? (Do those not work on a 404?)
If "Servers must not locate the actual change password page at the change password url" I would expect servers redirect to the actual change password page as a response. However "Clients must handle ok status responses", how would such response should be handled? I guess it should be handled anyway as a valid response, would be great to clarify.
https://github.com/WICG/change-password-url/blob/5ea606f98f1282502fd9e4892d75b1135c5f9751/index.bs#L85
The text was updated successfully, but these errors were encountered: