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
My example shows ckanr bumping into a federated login, which re-directs the API call to the login page (and returns HTTP status 200).
As "200" is no error code, ckanr doesn't pick this up as a problem - we'd need to test for "is this valid HTTP response an API response".
It's definitely a silly thing on our end (shouldn't our HTTP status be in the "redirected" 300 range?), but the error message I got was confusing at first.
Example: authentication error on
package_show
expects JSON by default, but chokes on the HTTP page with the error message:Would it be worth the effort to catch HTTP errors e.g. somewhere here?
The text was updated successfully, but these errors were encountered: