-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
[BUG] 404 when trying to "Add as redirect" in "Failures" #307
Comments
🙈 |
I assume that changing this line:
to: as what was done in:
would hopefully also fix it in FailuresTab EDIT: The above alone won fix the issue. In order to fix it, I had to changed the above and also change this line: retour-for-kirby/src/extensions/dialogs.php Line 142 in b74f547
to: |
✅ |
Describe the bug
The release 4.2.0 fixed the bug #300 when editing or removing path containing slashes from "Routes". Thank you!
However, the bug is still present when trying to "Add as redirect" from "Failures", which results in 404 error as described in #300
This bug is only present on Apache when the
AllowEncodedSlashes
is set toOff
Steps to reproduce
distantnative/retour-for-kirby
git clone https://github.com/getkirby/starterkit.git cd starterkit composer require distantnative/retour-for-kirby
Dockerfile
with following contenthttp://localhost/sub/not-existing
Rredirect
>Failures
andAdd as redirect
the previously called non-existent URLResult:
404 Not Found
from ApacheNote
Removing path containing slashes under
Failures
also results in 404 errorExpected behavior
modal opens up in order to add the path as redirect
Context
AllowEncodedSlashes Off
The text was updated successfully, but these errors were encountered: