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
I don't think the conformance testing suite should care about whether a redirect is using an absolute or relative URI, but maybe I am missing something.
Basically, verified-fetch is redirecting to an absolute URI, and the host of the absolute URI matches the host of the requested resource, so we could return a relative reference, but I don't think we should need to.
I don't think the conformance testing suite should care about whether a redirect is using an absolute or relative URI, but maybe I am missing something.
Basically, verified-fetch is redirecting to an absolute URI, and the host of the absolute URI matches the host of the requested resource, so we could return a relative reference, but I don't think we should need to.
See https://httpwg.org/specs/rfc9110.html#field.location
The text was updated successfully, but these errors were encountered: