[wp-trac] [WordPress Trac] #13909: Redirect does not return a HTTP body

WordPress Trac wp-trac at lists.automattic.com
Wed Jun 16 10:50:13 UTC 2010


#13909: Redirect does not return a HTTP body
--------------------------+-------------------------------------------------
 Reporter:  hakre         |       Owner:                
     Type:  defect (bug)  |      Status:  new           
 Priority:  normal        |   Milestone:  Future Release
Component:  General       |     Version:  3.0           
 Severity:  normal        |    Keywords:  needs-patch   
--------------------------+-------------------------------------------------
Changes (by dd32):

  * keywords:  has-patch tested => needs-patch
  * milestone:  3.1 => Future Release


Comment:

 This will not fare well in its current state.

 Take a Plugin activation command for example, Current workflow is
 Request->Redirect(error occured)->Activate plugin->Redirect(final
 activated)->End of process -> Redirect occurs to the last url

 With this patch, Output will be generated after the first redirect,
 causing the 2nd redirect to fail (as headers will already be sent).

 For front end queries it may make sense to offer some form of redirection
 text, I'm not supporting it on the back end however, Its an extra level of
 complication which just isn't needed.

 A user disabling their redirection handling is bound to suffer because of
 their choices, Opera for example, generates a content near exact to that
 example HTML you provided transparently when it blocks a redirection. Its
 the browsers option to ignore Redirects, Its the browsers responsibility
 to handle that redirect..

 Moving this out of 3.1 to Future Release, pending a commitor taking this
 for 3.1

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


More information about the wp-trac mailing list