Skip to content
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

URL Rewrites redirect loop #20309

Closed
mrmoonlv opened this issue Jan 15, 2019 · 16 comments · Fixed by #26902
Closed

URL Rewrites redirect loop #20309

mrmoonlv opened this issue Jan 15, 2019 · 16 comments · Fixed by #26902
Assignees
Labels
Component: Backend Component: UrlRewrite Event: cd-cologne19 Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: done Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@mrmoonlv
Copy link

Preconditions (*)

  1. PHP 7.1
  2. Magento version 2.2.6

Steps to reproduce (*)

  1. Go To Admin Url rewrites.
  2. Create New Url rewrite with request-path: / and target_path / with 301 or 302 redirect./

Expected result (*)

  1. Validation errors, that there will be infinite redirecion loop

Actual result (*)

  1. Browser error:
    This page isn’t working. redirected you too many times.
    Try clearing your cookies.
    ERR_TOO_MANY_REDIRECTS
@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jan 15, 2019
@magento-engcom-team
Copy link
Contributor

Hi @mrmoonlv. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@mrmoonlv do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no

@ghost ghost self-assigned this Jan 15, 2019
@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented Jan 15, 2019

Hi @SikailoISM. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@ghost
Copy link

ghost commented Jan 15, 2019

@magento-engcom-team give me 2.2.6 instance

@magento-engcom-team
Copy link
Contributor

Hi @SikailoISM. Thank you for your request. I'm working on Magento 2.2.6 instance for you

@magento-engcom-team
Copy link
Contributor

Hi @SikailoISM, here is your Magento instance.
Admin access: https://i-20309-2-2-6.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

@ghost ghost added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Component: UrlRewrite labels Jan 15, 2019
@shikhamis11 shikhamis11 self-assigned this Jan 15, 2019
@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented Jan 15, 2019

Hi @shikhamis11. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@surabhisrivastava09 surabhisrivastava09 self-assigned this Jan 15, 2019
@magento-engcom-team
Copy link
Contributor

Hi @Surabhi-Cedcoss. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@ghost ghost added the Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release label Jan 15, 2019
@ghost
Copy link

ghost commented Jan 15, 2019

@magento-engcom-team give me 2.3-develop instance

@magento-engcom-team
Copy link
Contributor

Hi @SikailoISM. Thank you for your request. I'm working on Magento 2.3-develop instance for you

@magento-engcom-team
Copy link
Contributor

Hi @SikailoISM, here is your Magento instance.
Admin access: https://i-20309-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

@ghost ghost added Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Jan 15, 2019
@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jan 15, 2019
@magento-engcom-team
Copy link
Contributor

@SikailoISM Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97640, MAGETWO-97641 were created

@ghost ghost mentioned this issue Jan 15, 2019
4 tasks
@shikhamis11 shikhamis11 removed their assignment Jan 15, 2019
@orlangur
Copy link
Contributor

@mrmoonlv @SikailoISM system works correctly as per configuration, what could be the reason to specify such request and target path?

@mrmoonlv
Copy link
Author

@orlangur, Yes: “system works correctly as per configuration”, but:

Fot configuration where request pahts == target paths, no dev user can break a whole webpage with never ending redirection loop.

Ofcourse: no one systems isnt secure to prevent foolish secure UX

@ghost ghost removed their assignment May 17, 2019
@mautz-et-tong mautz-et-tong self-assigned this Nov 29, 2019
@m2-assistant
Copy link

m2-assistant bot commented Nov 29, 2019

Hi @mautz-et-tong. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

  • 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 2. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 3. If the issue is not relevant or is not reproducible any more, feel free to close it.


mautz-et-tong pushed a commit to mautz-et-tong/magento2 that referenced this issue Nov 29, 2019
This adds a meaningful exception if request path equals target path on url rewrite edit page in admin
@ghost ghost unassigned mautz-et-tong Jan 14, 2020
@ghost ghost assigned Bartlomiejsz Feb 17, 2020
@Bartlomiejsz Bartlomiejsz linked a pull request Feb 17, 2020 that will close this issue
4 tasks
Bartlomiejsz added a commit to Bartlomiejsz/magento2 that referenced this issue Feb 18, 2020
Bartlomiejsz added a commit to Bartlomiejsz/magento2 that referenced this issue Feb 26, 2020
@magento-engcom-team magento-engcom-team added the Fixed in 2.4.x The issue has been fixed in 2.4-develop branch label Mar 12, 2020
@magento-engcom-team
Copy link
Contributor

Hi @mrmoonlv. Thank you for your report.
The issue has been fixed in #26902 by @Bartlomiejsz in 2.4-develop branch
Related commit(s):

The fix will be available with the upcoming 2.4.0 release.

magento-engcom-team added a commit that referenced this issue Mar 12, 2020
 - Merge Pull Request #26902 from Bartlomiejsz/magento2:feature/fix_20309_url_rewrites_redirect_loop
 - Merged commits:
   1. 684b951
   2. 0fd6fd3
@chamarts
Copy link

whats temporary fix for this ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Backend Component: UrlRewrite Event: cd-cologne19 Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: done Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants