[wp-trac] [WordPress Trac] #13689: multisite noblogredirect set, 404 error result not sending proper info with IIS

[WordPress Trac]

#13689: multisite noblogredirect set, 404 error result not sending proper info with
IIS
--------------------------+-------------------------------------------------
 Reporter:  Frumph        |       Owner:                
     Type:  defect (bug)  |      Status:  new           
 Priority:  normal        |   Milestone:  Future Release
Component:  General       |     Version:  3.0           
 Severity:  normal        |    Keywords:                
--------------------------+-------------------------------------------------
Changes (by wpmuguru):

  * keywords:  dev-feedback =>


Comment:

 Replying to [comment:24 ruslany]:
 >
 > 2. NOBLOGREDIRECT is used for bad URL's on the main site instead of a
 main site's 404 web page. Is this an incorrect behavior or is this by
 design? This is caused by the maybe_redirect_404() function and it looks
 to me that it has been like this for a while. Note that this issue is not
 specific to IIS.
 >
 It does that by design. In a subfolder install, if no sub-site matches the
 request WordPress (and before that MU) cannot tell whether it's a request
 for a non-existent sub site or a request for a non-existent page on the
 main site. So, one function served by the 404 handling is to provide
 consistent handling.

 Secondly, the main site is the default site which handles all requests
 WordPress that fail a sub-site lookup. After failing sub-site lookup, the
 buck stops at a 404 on the main site.

 The NOBLOGREDIRECT allows a super admin to direct those requests to
 something other than a 404 through the main site. There is no requirement
 to have a NOBLOGREDIRECT defined.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/13689#comment:26>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software