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
When using non-HTTPS server URL for HTTPS-only servers, the redirect is not followed, leading to an unusable API experience. The user should either be notified, or the redirects should be followed automatically.
Example log: 2023-05-14T11:53:48.034006Z [threadpool-daemon-1] [ApiV2Wrapper] 'POST http://runciv.hopfenspace.org/api/v2/auth/login': 301 Moved Permanently (42 ms)
The text was updated successfully, but these errors were encountered:
The detection of the API works smoothly. I suspect that POST requests are not repeated to the new destination (= not following the 301), but they are required for login and other actions.
When using non-HTTPS server URL for HTTPS-only servers, the redirect is not followed, leading to an unusable API experience. The user should either be notified, or the redirects should be followed automatically.
Example log:
2023-05-14T11:53:48.034006Z [threadpool-daemon-1] [ApiV2Wrapper] 'POST http://runciv.hopfenspace.org/api/v2/auth/login': 301 Moved Permanently (42 ms)
The text was updated successfully, but these errors were encountered: