[HN Gopher] Why do browsers not keep status 302 pages in back-bu...
       ___________________________________________________________________
        
       Why do browsers not keep status 302 pages in back-button history?
        
       Author : OJFord
       Score  : 25 points
       Date   : 2021-04-23 21:12 UTC (1 hours ago)
        
 (HTM) web link (stackoverflow.com)
 (TXT) w3m dump (stackoverflow.com)
        
       | chenxiaolong wrote:
       | I wish there was a way to keep _all_ redirects in the back button
       | history. For me, one of the most infuriating things on my work
       | computer was starting up the browser after a period of inactivity
       | (eg. the weekend) and seeing every Jira /Github/whatever tab
       | sitting at the corporate SSO page. The original page wouldn't be
       | in the back history so I effectively "lost" those tabs. Firefox
       | fortunately keeps most tabs suspended on startup nowadays so it's
       | less of an issue.
        
       | Denvercoder9 wrote:
       | Because when the original URL always gives a 302, that creates a
       | terrible user experience: hitting back would give you the
       | _current_ page again. Browsers can 't know whether a 302 is
       | transient or persistent.
        
         | OJFord wrote:
         | Good point, though that would only be a problem if you let it.
         | If you click-hold the back button in the browser 'chrome' you
         | typically get a list from history. (I'm not actually sure if
         | this behaviour is also present in actual history.) You could
         | skip past ongoing temporary redirects using that feature; it is
         | already necessary when that behaviour is implemented in
         | JavaScript instead of standard HTTP status codes.
        
       ___________________________________________________________________
       (page generated 2021-04-23 23:01 UTC)