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

fix: next.js rewrites were not respected for rest api #10759

Merged
merged 2 commits into from
Jan 23, 2025
Merged

fix: next.js rewrites were not respected for rest api #10759

merged 2 commits into from
Jan 23, 2025

Conversation

r1tsuu
Copy link
Member

@r1tsuu r1tsuu commented Jan 23, 2025

Fixes #10655

@r1tsuu r1tsuu changed the title fix: next.js rewrites were not respected for api fix: next.js rewrites were not respected for rest api Jan 23, 2025
@DanRibbens DanRibbens merged commit c0ae994 into main Jan 23, 2025
67 checks passed
@DanRibbens DanRibbens deleted the fix/nextjs-rewrites- branch January 23, 2025 18:36
@github-actions GitHub Actions
Copy link
Contributor

🚀 This is included in version v3.19.0

@teawithfruit
Copy link

teawithfruit commented Feb 4, 2025 •
edited
Loading

This change results in GraphQL no longer working in CORS environments because REST_OPTIONS is also used in GraphQL.
https://github.com/payloadcms/payload/blob/v3.19.0/app/(payload)/api/graphql/route.ts

However, a slug is not present in a GraphQL URL.

https://discord.com/channels/967097582721572934/967097582721572937/1336289208104386591

Update:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@DanRibbens DanRibbens DanRibbens approved these changes

Assignees
No one assigned
Labels
created-by: Payload team
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Next.js rewrites configuration is not working from 3.16.0
3 participants
@r1tsuu @teawithfruit @DanRibbens