-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If Shiori is behind a reverse proxy (patch with --webroot option), the extension doesn't connect anywhere but the root of the URL. #21
Comments
I proposed a fix through #32 |
Has this been fixed by #32? If so, how do I actually use it? I tried using the base URL "https://[omitted]/shiori/" in the "Server" field in the configuration, but it must be talking to the wrong URL, because I get a HTTP 404 from the server. |
I just checked what I have: I start (I suppose you are self-hosting this). |
Oh, maybe my trailing slash ( |
Hey @l0b0, are you using the latest release or the latest master? |
This commit fixes by making the
new URL
calls append the API path to the server URL config string instead of using 2 parameters to the URL() function.The text was updated successfully, but these errors were encountered: