WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #16158


Ignore:
Timestamp:
01/08/11 21:22:03 (4 years ago)
Author:
ocean90
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16158

    • Property Version changed from to 3.0.1
  • Ticket #16158 – Description

    initial v1  
    77Below is a debug dump I hack in the WP_HTTP->request call coming from wp_version_check.  I pasted the URL use into the browser bar it returned the correct information.  Called from wordpress localhost, api.wordpress.com returns a HTML document with the <title>Page not found</title> and a bunch of info about wordpress. 
    88 
     9 
     10{{{ 
    911[08-Jan-2011 20:42:48] URL='http://api.wordpress.org/core/version-check/1.5/?version=3.0.1&php=5.3.2-1ubuntu4.5&locale=en_US&mysql=5.0.83&local_package=&blogs=1&users=2&multisite_enabled=0' 
    1012[08-Jan-2011 20:42:48] r=array ( 
     
    3133  'local' => false, 
    3234) 
     35}}} 
     36 
    3337 
    3438So two problems: 
    3539 
    36 1) If the local site core check fails, it assumes what it is running is the most current.  There is no indication that the core check failed.  It seems like the "Page Not Found" page returned from api.wordpress.org should be displayed. See 16156, 16094 for similar issues. 
     401) If the local site core check fails, it assumes what it is running is the most current.  There is no indication that the core check failed.  It seems like the "Page Not Found" page returned from api.wordpress.org should be displayed. See #16156, #16094 for similar issues. 
    3741 
    38422) What in the request is causing the HTTP get to fail?  I think it must something in the header information.  BUT, it USED to work.  Is the server behaving differently?