WordPress.org

Make WordPress Core

Changes between Initial Version and Version 5 of Ticket #10624


Ignore:
Timestamp:
12/22/09 09:20:01 (4 years ago)
Author:
dd32
Comment:

I am surprised that HEAD requests follow the redirects and I would expect to get the HEAD results back and read the information out.

Me too, I'll write in a patch for that - Damn, it'll create conflicts with all my other HTTP patches from this evening :)

As for returning the redirected url - which of the many urls would you return?

The last one. However, You're right i think, Its not really a typical use-case.. It'd be a pretty rare occurance.

Lets skip returning the URL, and stick to preventing redirects for Head requests.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10624

    • Property Cc westi added
    • Property Keywords needs-patch added; dev-feedback removed
    • Property Summary changed from Upon redirection limit being hit return redirected URL in wp_error data fields to Redirection should be disabled for HEAD requests
    • Property Milestone changed from 2.9 to Future Release
  • Ticket #10624 – Description

    initial v5  
     1Updated: 
     2 
     3Currently, HEAD requests will follow redirections in some(or all) transports. HEAD requests should not follow redirects. 
     4 
     5---- 
     6Original: 
     7 
    18Currently if you request a URL that attempts to redirect past your redirection limit, you'll get a object similar to this: 
    29