[wp-trac] Re: [WordPress Trac] #10098: Turbo failed

WordPress Trac wp-trac at lists.automattic.com
Thu Jun 11 16:51:10 GMT 2009


#10098: Turbo failed
-------------------------------+--------------------------------------------
 Reporter:  csseur3            |        Owner:          
     Type:  defect (bug)       |       Status:  reopened
 Priority:  normal             |    Milestone:  2.8.1   
Component:  Administration     |      Version:  2.8     
 Severity:  normal             |   Resolution:          
 Keywords:  reporter-feedback  |  
-------------------------------+--------------------------------------------

Comment(by sivel):

 A 403 is a 403.  A 404 does not get converted to a 403 because directory
 indexing is disabled.  Directory indexing just prevents you from seeing a
 file list when browsing to the directory.  It would not cause a 403 unless
 the file or the apache configuration is preventing access to the file.

 As anyone in the httpd IRC channel would say:

 Whatever the problem, step one is to look in the error log (and any other
 logs that may apply, such as suexec, mod_rewrite, or mod_security).

 Once you can confirm why the 403 is being returned, which the apache error
 log will tell you, we can rule this out as being a WordPress issue.

 I have tested that this file is accessible on all 28 servers that I run
 WordPress 2.8 on currently and none of them are experiencing this problem.

 For the time being we will leave this ticket open until you give us the
 snippet of apache error log related to this 403.

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


More information about the wp-trac mailing list