-
Notifications
You must be signed in to change notification settings - Fork 17
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
redirect loop #111
Comments
Experiencing the same issue, but only on one redirect in thousands. |
So we ditched this module and wrote our own. In server middleware we have
This works for all redirect objects passed to it, extensively tested on over 4k varying redirects. |
Fantastic. thank you @Webbist-dev . |
@Webbist-dev could you explain what the methods inside Also presumably this does not accept regex redirects? |
Inspired by the code supplied by @Webbist-dev , I've found an adjusted working solution for our setup to meet the following requirements:
My solution to replace the requirement for the Nuxt Redirect-Module: OPTIONAL – for those who need to query an endpoint for redirects array, In
REQUIRED – in
And lastly, in
|
Hi, I've been struggling with this issue too since days. Before : I don't know if there is some issue with the spelling between "simple quote / double quote", regex mode in the from attribute but it works like this, no need for a middleware. Regards, |
I have the following redirect which seem to cause an infinite redirect loop. I can't quite figure out why.
Do you know why this might be happening? If not, is there a way to set up some kind of log or debugger to track what the redirect module is actually doing behind the scenes for each redirect?
This is the rule:
/get-the-positive-edge => /forms/get-the-positive-edge
And this is what happens when I enter
/get-the-positive-edge
into the browser:/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/forms/get-the-positive-edge
The text was updated successfully, but these errors were encountered: