[wp-trac] [WordPress Trac] #6778: Detect when the config will cause infinite loop

[WordPress Trac]

#6778: Detect when the config will cause infinite loop
-------------------------------------+--------------------------------------
 Reporter:  Analogpoint              |        Owner:  anonymous     
     Type:  enhancement              |       Status:  reopened      
 Priority:  normal                   |    Milestone:  Future Release
Component:  Permalinks               |      Version:  2.5           
 Severity:  normal                   |   Resolution:                
 Keywords:  needs-patch 2nd-opinion  |  
-------------------------------------+--------------------------------------
Changes (by dd32):

  * keywords:  needs-patch => needs-patch 2nd-opinion


Comment:

 > Use the HTTP API to request the new URL, and check to see if it gets
 redirected back to the current URL? (That'd require setting an extra param
 to tell the canonical redirection code from kicking in again possibly?)

 > attachment test.php added
  * relies upon patch from #10624
  * Sample implementation of the above idea, Probably contains a few extra
 cases that dont need to be included
   * Just the ok/redirect/error items maybe.
  * The spinner on an unsupported attempt could confuse people to think
 that WordPress just auto-saved the field.
   * unsupported = no HTTP transports available which can support
 redirection and report back issues.

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