[wp-trac] [WordPress Trac] #16887: Increase the default number of maximum redirects to 20

[WordPress Trac]

#16887: Increase the default number of maximum redirects to 20
-----------------------------+------------------------------
 Reporter:  hakre            |       Owner:
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  HTTP             |     Version:  3.1
 Severity:  normal           |  Resolution:
 Keywords:                   |
-----------------------------+------------------------------

Comment (by dd32):

 > 20 sounds absolutely absurd.

 I do agree, 10 seems like an upper limit to consider, but even that seems
 too high.

 > I think it may become important to start looking for redirection loops

 That came into my head as well, break if the location being requested has
 already been requested with the same params?  I can see that causing issue
 though for someone, ie: `/node/something/ => /create/something/ =>
 /node/something/` - not that I'd ever recommend someone do that, but I can
 see someone implementing that

 Setting an upper soft limit (ie. changeable upon request) of a sane value
 sounds better to me; 7 is a nice human-random number in the right range,
 but still has the 'low' look to it.

 The downside to having the redirects too large is the latency in requests,
 it can easily add up to 1s waiting for a HTTP response right now, and
 thats on a reasonable connection (200ms is not unreasonable for a single
 request, anything up to 500ms should be assumed to be a reasonable
 redirection response IMO), so going too high can introduce perceived
 slowness (even when it's not !WordPress's fault that a plugin has made a
 request for a infinite-redirecting document)

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