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
In the Auth2 branch we currently use "HTTP equivalent" status codes for the probe service status. We describe these as "The HTTP status code that would be returned for the resource for which this is a Probe Service.". However, in the video 302 / location example, the likely actual response would be 401 if one tried to access the original access-controlled resource ... but we still want to treat it like a 302 and access the location
The text was updated successfully, but these errors were encountered:
Resolved. In Auth 2.0 have Probe Service where status is described as "The HTTP status code that would be returned for the access-controlled resource.". The location property must only be included for 30x response https://iiif.io/api/auth/2.0/#location
In the Auth2 branch we currently use "HTTP equivalent" status codes for the probe service
status
. We describe these as "The HTTP status code that would be returned for the resource for which this is a Probe Service.". However, in the video 302 /location
example, the likely actual response would be 401 if one tried to access the original access-controlled resource ... but we still want to treat it like a 302 and access thelocation
The text was updated successfully, but these errors were encountered: