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

Redirect with 4xx not working #49

Closed
kwissem1 opened this issue Nov 4, 2021 · 1 comment
Closed

Redirect with 4xx not working #49

kwissem1 opened this issue Nov 4, 2021 · 1 comment

Comments

@kwissem1
Copy link

kwissem1 commented Nov 4, 2021

Prerequisites

We do our best to reply to all the issues on time. If you will follow the given guidelines, the turn around time will be faster.

  • Lots of raised issues are directly not bugs but instead are design decisions taken by us.
  • Make use of our forum, or discord server, if you are not sure that you are reporting a bug.
  • Ensure the issue isn't already reported.
  • Ensure you are reporting the bug in the correct repo.

Delete the above section and the instructions in the sections below before submitting

Package version

5.5.7

Node.js and npm version

14.18.1

Sample Code (to reproduce the issue)

Route.get('/test', async ({ response }) => { return response.status(404).redirect().toPath('/path') })

Response: Redirecting to /path

BONUS (a sample repo to reproduce the issue)

@RomainLanz
Copy link
Member

Hey @kwissem1! 👋🏻

If you are not more describing your issue, we will keep closing it.

Redirecting somewhere should be a 301, 302, 307 or 308.
It makes no sense to send back a 404 when redirecting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants