[wp-trac] [WordPress Trac] #13689: multisite noblogredirect set, 404 error result not sending proper info with IIS
WordPress Trac
wp-trac at lists.automattic.com
Wed Jun 2 01:01:31 UTC 2010
#13689: multisite noblogredirect set, 404 error result not sending proper info with
IIS
--------------------------+-------------------------------------------------
Reporter: Frumph | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: 3.0
Component: General | Version: 3.0
Severity: normal | Keywords: Multisite Subdomain 404
--------------------------+-------------------------------------------------
Scenario. With NOBLOGREDIRECT specified as the main sites url, the 404
errors and the bad blog url are supposed to go what is specified as the
location in the noblogredirect define.
The bug is the 404 errors are *not* pointing to what is specified in the
noblogredirect, the 404 errors (that are not bad blog urls) are triggering
an IIS error response and not redirecting.
When it's done triggering the IIS error it then uses the web.config to
transfer to the main site.
Besides this bug.
This tells me 2 things, this tells me that the method/behavior of this is
wrong and should be looked at. *if* wordpress knows the difference
between a bad blogurl and a 404 error page, the 404 error *should* go to
the 404 template, however in the past WPMU versions it did not do that it
went straight to the mainsite as well. It *should* go to the 404
template and since it knows the difference it should be coded a such.
1) Bad subdomains should go to the specified noblogredirect define.
2) 404 error pages should go to the 404 page template for the theme.
Not to mention that the bug in question *is* that the 404 error itself is
not redirecting to it's intended location to begin with.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/13689>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list