[wp-trac] [WordPress Trac] #14062: plugins.php violates Location Header HTTP 1.1 Specification

[WordPress Trac]

#14062: plugins.php violates Location Header HTTP 1.1 Specification
--------------------------+-------------------------------------------------
 Reporter:  hakre         |       Owner:            
     Type:  defect (bug)  |      Status:  new       
 Priority:  normal        |   Milestone:  Unassigned
Component:  HTTP          |     Version:  3.0       
 Severity:  normal        |    Keywords:            
--------------------------+-------------------------------------------------
 While being on my HTTP related work lately I came over another issue. Many
 Redirects are violating the HTTP RFC in a way that the Location header is
 not containing an absolute URI as of which is to be used:

    The Location response-header field is used to redirect the recipient
    to a location other than the Request-URI for completion of the
    request or identification of a new resource. For 201 (Created)
    responses, the Location is that of the new resource which was created
    by the request. For 3xx responses, the location SHOULD indicate the
    server's preferred URI for automatic redirection to the resource. The
    field value consists of a single absolute URI.

        Location       = "Location" ":" absoluteURI

    An example is:

        Location: http://www.w3.org/pub/WWW/People.html

 [http://tools.ietf.org/html/rfc2616#section-14.30 14.30 Location/RFC 2616;
 HTTP/1.1; June 1999]

 When I analyze the output, I get the following location header line:

     Location: plugins.php?deactivate=true&plugin_status=active&paged=1

 This is a relative URI, not a absolute one.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14062>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software