For self-hosted backends, it can happen that the reverse proxy is not configured correctly. When this happens the initial requests to e.g. https://wger.my-domain.com:1234/api/v2/endpoint work well, but the pagination links next and previous are constructed by the backend from these headers so in case of a misconfiguration these could look like http://localhost/api/v2/endpoint?limit=... which will not work (or they might work in the home lab but not outside, etc. etc.).
Idea: add a sanity check after login (perhaps similar to the min server version check) that tries to hit an endpoint like the exercise one and checks that the domain returned in the next link is the same as the one used to login and if not show some information to the user.
For self-hosted backends, it can happen that the reverse proxy is not configured correctly. When this happens the initial requests to e.g.
https://wger.my-domain.com:1234/api/v2/endpointwork well, but the pagination linksnextandpreviousare constructed by the backend from these headers so in case of a misconfiguration these could look likehttp://localhost/api/v2/endpoint?limit=...which will not work (or they might work in the home lab but not outside, etc. etc.).Idea: add a sanity check after login (perhaps similar to the min server version check) that tries to hit an endpoint like the exercise one and checks that the domain returned in the next link is the same as the one used to login and if not show some information to the user.