Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Bug 1362438: additional redirects from SCL3 Apache to Django #4231
This was referenced
Jul 18, 2017
OK, here's what's happening. The failing test is requesting this path:
This is because
So, the redirect pattern uses the rule:
to redirect to:
breaking the test, which is trying to detect MindTouch URLs like
In any case, URL patterns that are trying to detect locales (this one and a few others) need to lean on
I think I own this PR now, having made @metadave wait over 2 months for me to figure it out.
@@ Coverage Diff @@ ## master #4231 +/- ## ========================================== + Coverage 88.32% 88.33% +<.01% ========================================== Files 163 163 Lines 10229 10233 +4 Branches 1420 1420 ========================================== + Hits 9035 9039 +4 Misses 968 968 Partials 226 226
Aug 3, 2017
1 check passed
As part of mozmeao/infra#436, I took a look at what's left from the Apache config.
These files are periodically generated, and accessed by Google and others to see what is new. We'll need to serve these from Django instead. If we move
This must have been the way to load pages in the MediaWiki/DekiWiki days. I looked at the requests and they are roughly:
I don't see any reason to handle these requests, and they should return 404s
This is tracked in bug 962148. This rule serves up the duplicate content under a different URL, and instead we want a permanent redirect.
This is the Apache alias for the Django modwsgi handler, and it not needed in AWS.
To determine the impact of these rules, I looked the the Apache access logs on developer1, which is one of six servers for developer.mozilla.org, developer.cdn.mozilla.net, and mozillademos.org.
Update 1: We do have recent changes feeds. I still think we should 404 the requests to the legacy feeds, rather than redirect them to "Create a New Page".