Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

[Feature]: Allow hard redirect() on the same domain #9634

Closed
machour opened this issue Nov 24, 2022 · 1 comment
Closed

[Feature]: Allow hard redirect() on the same domain #9634

machour opened this issue Nov 24, 2022 · 1 comment
Labels

Comments

@machour
Copy link
Contributor

machour commented Nov 24, 2022

What is the new or updated feature that you are suggesting?

Continued from the conversation with @brophdawg11 in #9590 (comment)

I'm currently migrating a PHP app to Remix, and doing it incrementally thanks to nginx:

  • mydomain.com/a is handled by PHP
  • mydomain.com/b is handled by Remix

If I do a redirect() from /b to /a, Remix tries to handle it like it's one of his routes, and it fails.
We need to be able to do a same domain "hard" redirect.

One of the solutions could be to consider absolute redirects as hard redirects, and keeping relative ones as SPA redirections.

Why should this feature be included?

This would make it easier for folks to gradually migrate an online website, and would provide a happy path doing so.

My current workaround is to redirect from /b to a subdomain which in turns redirects again to /a, which is far from ideal.

@machour machour changed the title [Feature]: [Feature]: Allow hard redirect() on the same domain Nov 24, 2022
@brophdawg11
Copy link
Contributor

I'm going to convert this to a discussion so it can go through our new Open Development process. Please upvote the new Proposal if you'd like to see this considered!

@remix-run remix-run locked and limited conversation to collaborators Jan 9, 2023
@brophdawg11 brophdawg11 converted this issue into discussion #9859 Jan 9, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
None yet
Development

No branches or pull requests

2 participants