![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
#20484 closed defect (bug) (fixed)
Re-enable redirect_canonical for IIS
| Reported by: | amattie | Owned by: | markjaquith |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.5 |
| Component: | Canonical | Version: | |
| Severity: | normal | Keywords: | 3.5-early |
| Cc: | Focuses: |
Description
Canonical redirects within IIS 7 were disabled in #16639. The comment then was "The time between 3.1 and 3.2 should be much shorter than the 3.0-3.1 release cycle, so waiting for 3.2 is a tradeoff that many should be able to make." Now that it's been > 1yr and 3.4 is right around the corner, would it be possible for this issue to be revisited?
I develop in Windows / IIS7 and deploy to Linux and so the functionality mismatch caused me a bit of grief until I figured out what was going on. As others have pointed out, it seems silly to discriminate against a perfectly good web server that would otherwise handle redirects just fine.
Change History (9)
#2
@
14 years ago
- Keywords 3.5-early added
- Milestone Awaiting Review → Future Release
Sorry this got lost.
#6
@
14 years ago
- Resolution fixed
- Status closed → reopened
[21207] (which came from whatever [17492] reverted, I know) has some logic issues. If you're on IIS6, you end up with canonical redirects. This is quite possibly what the original bug was in #16639...
What this should be is || ( $is_IIS && ! iis7_supports_permalinks() ). Thus, if you're on IIS (any version), you don't get canonical redirects, unless you have IIS7 and it supports permalinks.
+1