Describe the bug
When accessing the server via a reverse proxy, the Sorayomi app shows "308" as an error and the request is not completed & the chapters remain unread. This only happens when using a reverse proxy set up with a http to https redirect to access the server.
Obviously, "308" permanent redirect is being interpreted by Sorayomi as an error (I'm assuming it just checks for non-2xx status codes). After updating the server URL to explicitly include "https", this is no longer an issue.
To Reproduce
Steps to reproduce the behavior:
Have a reverse proxy behind a domain name that serves traffic to Tachidesk server.
Expected behavior
Marking as read should still work as expected. Even though this is easily fixed by including "https" explicitly in the URL, a 308 redirect is pretty standard.
Screenshots
Probably not necessary, but will add if requested.
Device information (Server)
Tachidesk version: v0.7.0-r1487
Server Operating System: Ubuntu 22.04.3
Server Desktop Environment: N/A (headless server)
Server JVM version: N/A (using most recent preview release of suwayomi/tachidesk:preview docker image)
Describe the bug When accessing the server via a reverse proxy, the Sorayomi app shows "308" as an error and the request is not completed & the chapters remain unread. This only happens when using a reverse proxy set up with a http to https redirect to access the server. Obviously, "308" permanent redirect is being interpreted by Sorayomi as an error (I'm assuming it just checks for non-2xx status codes). After updating the server URL to explicitly include "https", this is no longer an issue.
To Reproduce Steps to reproduce the behavior:
Expected behavior Marking as read should still work as expected. Even though this is easily fixed by including "https" explicitly in the URL, a 308 redirect is pretty standard.
Screenshots Probably not necessary, but will add if requested.
Device information (Server)
suwayomi/tachidesk:previewdocker image)Device information (Client)