-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Exact Redirect between version doesn't work without slash #9507
Comments
…hout slash This commit adds a javascript redirect to handle the redirection of page like https://slicer.readthedocs.io/en/v5.0 to https://slicer.readthedocs.io/en/v5.0/ and workaround limitation documented in readthedocs/readthedocs.org#9507 Indeed, despite of adding the following "Exact Redirect" to the readthedocs configuration: ``` /en/v5.0 -> /en/5.0 /en/v5.0/$rest -> /en/5.0/ ``` , specifying https://slicer.readthedocs.io/en/v5.0 doesn't redirect to https://slicer.readthedocs.io/en/5.0
…hout slash This commit adds a javascript redirect to handle the redirection of page like https://slicer.readthedocs.io/en/v5.0 to https://slicer.readthedocs.io/en/v5.0/ and workaround limitation documented in readthedocs/readthedocs.org#9507 Indeed, despite of adding the following "Exact Redirect" to the readthedocs configuration: ``` /en/v5.0 -> /en/5.0 /en/v5.0/$rest -> /en/5.0/ ``` , specifying https://slicer.readthedocs.io/en/v5.0 doesn't redirect to https://slicer.readthedocs.io/en/5.0
…hout slash This commit adds a javascript redirect to handle the redirection of page like https://slicer.readthedocs.io/en/v5.0 to https://slicer.readthedocs.io/en/v5.0/ and workaround limitation documented in readthedocs/readthedocs.org#9507 Indeed, despite of adding the following "Exact Redirect" to the readthedocs configuration: ``` /en/v5.0 -> /en/5.0 /en/v5.0/$rest -> /en/5.0/ ``` , specifying https://slicer.readthedocs.io/en/v5.0 doesn't redirect to https://slicer.readthedocs.io/en/5.0
Hi! Have you tried from |
This should be fixed with #9557. And maybe the original redirect that has |
@stsewd @ericholscher we should create a test case for this particular issue 👍🏼 |
@jcfr can you confirm if you are still having this issue? We just deployed a potential fix and I quickly tested this by creating a redirect as I suggested in my previous comment (#9507 (comment)) and it worked! 👍🏼 |
Thanks for the update 🙏 I will follow up on Thursday when back on the computer. |
I confirm the fix works as expected: Before
After
|
@jcfr Thanks for the follow up and closing the issue 👍 |
Details
Expected Result
We are currently building documentation associated with branch Slicer@5.0 and setup an
Exact Redirect
from/en/v5.0/$rest
->/en/5.0/
And we were expecting the following to work:
Actual Result
Here is what we observe:
Setting up the additional redirect
Exact Redirect
from/en/v5.0
->/en/5.0
didn't help either.And there are still observing the following:
The text was updated successfully, but these errors were encountered: