404 page not found on one of the links
- Open this page: https://docs.djangoproject.com/foundation/corporate-membership/
- Click on 'Become a DSF corporate member'
- Follow the wrong link: https://docs.djangoproject.com/foundation/corporate-membership/join/ instead of https://www.djangoproject.com/foundation/corporate-membership/join/
Hi and thanks for the report!
The issue here is that the page /foundation/corporate-membership/ should not be available under the docs subdomain. It should only be available under the www domain (where the link works correctly).
I've had a quick look in the URL configuration of the project and I don't really understand why the page at https://docs.djangoproject.com/foundation/corporate-membership/ is available. From what I can see, only documentation pages should be served under the docs domain.
The page /foundation/corporate-membership/ returns a 404 error on the production environment but is working as expected - returns 404 - in the local setup.
-
Cannot replicate this issue in my local environment where it correctly returns a 404 error.
-
The URL
/foundation/corporate-membership/on a local setup works as expected, returning a 404 error. -
It's possible that
/foundation/corporate-membership/is being interpreted wrong on the production environment. -
More specifically,
/foundationgets matched as a language and/corporate-membershipas a version in the URL patterns. This could be the reason why it resolves the URL to something different and returns 404.
Steps Taken:
- Cross-checked how the URLs are handled and configured on the local setup.
They have verified that
DocumentReleaseand document path handling is right locally.
It seems the problem is particular to the configuration or data of the production environment because it doesn't show up on a local setup where everything works just fine. There is a need for further investigation into URL routing and pattern matching in the production environment.
Further more the latest version that i am using does not have this URL path at all /foundation/corporate-membership/
This was reported again in #1880 with some information about how to reproduce the issue and an idea for a fix. So I'll close this issue in favor of the other one. Thanks everyone! 🎸