[wp-trac] [WordPress Trac] #50422: Prevent Browser Caching From Getting Involved With wp_redirect and wp_safe_redirect (Leaving the Browser to Purely Honor the Redirect Code Used)

[WordPress Trac]

#50422: Prevent Browser Caching From Getting Involved With wp_redirect and
wp_safe_redirect (Leaving the Browser to Purely Honor the Redirect Code
Used)
-------------------------------------+------------------------------
 Reporter:  KZeni                    |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  General                  |     Version:  5.4.2
 Severity:  normal                   |  Resolution:
 Keywords:  needs-testing has-patch  |     Focuses:
-------------------------------------+------------------------------

Comment (by KZeni):

 Summary, why should browser caching be allowed to be potentially involved
 with a redirect when it should be up to the status code of the redirect to
 determine the permanence/behavior of the redirect? This just makes it so
 browser cache doesn't get in the way (be it a caching plugin, custom
 headers set by the site/server, etc.) and does so in a way that doesn't
 put it on plugin & other developers to account for this when it should be
 harmless (301 redirects should still be seen as such, little-to-no
 overhead, etc.) & only helpful (can help simplify code found elsewhere,
 prevent issues that may come up in certain circumstances, etc.) to have
 WordPress take care of it natively.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50422#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform