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
We are currently mixing layers between HTTP and the response payload. The client needs access to the status code (200 vs 4xx (vs 3xx?)) but also information from the body. We should limit to only one layer and just put everything in the JSON body. While this might not be appreciated by purists, it is much easier for implementers and they are our primary audience.
The latest version of the IIIF Authorization Flow 2.0 probe service has a property called status that has the value of the status that the service returned. This issue can be closed.
We are currently mixing layers between HTTP and the response payload. The client needs access to the status code (200 vs 4xx (vs 3xx?)) but also information from the body. We should limit to only one layer and just put everything in the JSON body. While this might not be appreciated by purists, it is much easier for implementers and they are our primary audience.
eg.
The text was updated successfully, but these errors were encountered: