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.

Sign up for GitHub

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

Jump to bottom

Mention HTTP 303 See Other in redirects section #35997

Merged
merged 3 commits into from
Apr 8, 2022
Merged

Mention HTTP 303 See Other in redirects section #35997

merged 3 commits into from
Apr 8, 2022

Commits on Apr 8, 2022

  1. Mention HTTP 303 See Other in redirects section 

    Migrating from express to nextjs API routes broke one of our APIs because of how `redirect` works in nextjs vs. how it works in express. We need to redirect the user to a confirmation page via GET after making a POST request, which is not possible with `redirect`.

HTTP 303 seems to be the way to go in that case and I think it should be mentioned here.
    Björn committed Apr 8, 2022
    Configuration menu
    Copy the full SHA
    ea12502 View commit details
    Browse the repository at this point in the history

  2. Update docs/api-reference/next/server.md 

    Co-authored-by: Steven <steven@ceriously.com>
    @styfle
    Björn and styfle committed Apr 8, 2022
    Configuration menu
    Copy the full SHA
    86ab42f View commit details
    Browse the repository at this point in the history

  3. Merge branch 'canary' into patch-2

    @kodiakhq
    kodiakhq[bot] committed Apr 8, 2022
    Configuration menu
    Copy the full SHA
    fe63f36 View commit details
    Browse the repository at this point in the history