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

Update custom-routes-proxying to use fallback rewrites #23610

Merged
merged 2 commits into from Apr 1, 2021

Conversation

ijjk
Copy link
Member

@ijjk ijjk commented Apr 1, 2021

This updates to use the new fallback rewrites support instead of the previous no-op rewrite workaround.

Documentation / Examples

  • Make sure the linting passes

@ijjk ijjk added the examples Issue/PR related to examples label Apr 1, 2021
@kodiakhq kodiakhq bot merged commit bfd36bd into vercel:canary Apr 1, 2021
@ijjk ijjk deleted the update/custom-routes-proxying branch April 1, 2021 16:49
SokratisVidros pushed a commit to SokratisVidros/next.js that referenced this pull request Apr 20, 2021
This updates to use the new `fallback` rewrites support instead of the previous no-op rewrite workaround. 


## Documentation / Examples

- [x] Make sure the linting passes
flybayer pushed a commit to blitz-js/next.js that referenced this pull request Apr 29, 2021
This updates to use the new `fallback` rewrites support instead of the previous no-op rewrite workaround. 


## Documentation / Examples

- [x] Make sure the linting passes
@vercel vercel locked as resolved and limited conversation to collaborators Jan 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
examples Issue/PR related to examples
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants