[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):

 The discussion here is related to #16888, the followlocation
 parameter/flag can help to keep things apart. The concept is borrowed from
 cUrl itself which has two settings as well (both sharing some scope):
 [http://curl.haxx.se/libcurl/c/curl_easy_setopt.html#CURLOPTFOLLOWLOCATION
 follow location] and
 [http://curl.haxx.se/libcurl/c/curl_easy_setopt.html#CURLOPTMAXREDIRS max
 redirects].

 Probably it's useful to have a redirection parameter (int), then a follow-
 location parameter (bool) and a max-redirects (int) parameter.

 The redirection paramter will set both as needed, and setting any of the
 others can override for fine-control. Transports internals can rely to the
 two more specific parameters if they need a more fine-grained control.

 (Informative: Next to those are two more redirection related curl
 settings:
 [http://curl.haxx.se/libcurl/c/curl_easy_setopt.html#CURLOPTPOSTREDIR post
 redir],
 [http://curl.haxx.se/libcurl/c/curl_easy_setopt.html#CURLOPTREDIRPROTOCOLS
 redir protocols].)

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