[wp-trac] [WordPress Trac] #16855: HTTP API No Follow Redirection

[WordPress Trac]

#16855: HTTP API No Follow Redirection
--------------------------+------------------------------
 Reporter:  TheDeadMedic  |       Owner:  dd32
     Type:  defect (bug)  |      Status:  reviewing
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  HTTP          |     Version:  3.1
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+------------------------------

Comment (by hakre):

 Replying to [comment:17 sivel]:
 > I'm not sure I like this idea. We should key off of the 'redirection'
 argument instead of introducing another argument.  If redirection > 0 we
 should assume that we want to follow the location.  We should be able to
 move the logic of determining whether or not we can follow out of an
 argument and use it closer to where we have the potential of running into
 issues.

 Give your thoughts a go and provide a patch so we can test how it feels.

 Some info on the current 'redirection' use: -1 is no limit on redirects
 for the !cUrl transport. For streams below one means that no redirects are
 followed. No idea if streams give an error on that one, cUrl does.

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