You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Accessing a non-existent page does notreturn an HTTP 404 status code. Instead, it returns a 200 status code, which can lead to issues with SEO and proper error handling.
To Reproduce
Set up a Next.js project using next-international.(Custom 404 Page set)
Expected behavior
The application should return an HTTP 404 status code when a user accesses a non-existent page, displaying a 404 error page accordingly.
Screenshots
N/A
About (please complete the following information):
next-international version [1.2.3]
Next.js version [14.2.0]
Additional context
This issue affects error handling and SEO, as search engines might index non-existent pages due to the incorrect status code
The text was updated successfully, but these errors were encountered:
Describe the bug
Accessing a non-existent page does notreturn an HTTP 404 status code. Instead, it returns a 200 status code, which can lead to issues with SEO and proper error handling.
To Reproduce
[...other]/page.tsx
middleware.ts
Expected behavior
The application should return an HTTP 404 status code when a user accesses a non-existent page, displaying a 404 error page accordingly.
Screenshots
N/A
About (please complete the following information):
Additional context
This issue affects error handling and SEO, as search engines might index non-existent pages due to the incorrect status code
The text was updated successfully, but these errors were encountered: