[wp-trac] Re: [WordPress Trac] #7456: Timeout in WP_Http_Streams::request causes Fatal error abort

[WordPress Trac]

#7456: Timeout in WP_Http_Streams::request causes Fatal error abort
---------------------+------------------------------------------------------
 Reporter:  wet      |        Owner:  anonymous
     Type:  defect   |       Status:  reopened 
 Priority:  normal   |    Milestone:  2.7      
Component:  General  |      Version:           
 Severity:  normal   |   Resolution:           
 Keywords:           |  
---------------------+------------------------------------------------------
Changes (by wet):

  * keywords:  has-patch needs-testing =>
  * status:  closed => reopened
  * resolution:  fixed =>

Comment:

 NB: Timeouts in fopen() now decorate the public facing website with a
 notice:
 {{{
 Warning: fopen(http://example.com/wp-cron.php?check=deadbeef)
 [function.fopen]: failed to open stream
 }}}

 Additionally, it effectively establishes a denial-of-service barrier to
 the backend as the PHP notices are '''the only output''' from a visit to
 http://example.com/wp-admin/ . The second notice is:
 {{{
 Warning: Cannot modify header information - headers already sent by
 (output started at /www/wp-includes/http.php:659) in /www/wp-
 includes/pluggable.php on line 770
 }}}

 Short-circuiting WP_Http_Streams::request() was the only way to regain
 admin access, see attached diff.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/7456#comment:4>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software