From: MikeE@ster.invalid   
      
   Lawrence D’Oliveiro wrote:   
   > On Fri, 7 Nov 2025 11:08:12 -0800, Mike Easter wrote:   
   >   
   >> gglAIov (google AI overview) has a nice discussion of reasons that a   
   >> webserver might use a temporary redirect:   
   >   
   > Say you have a site that requires authentication. You may have had a   
   > cookie from before, but it has since expired. You go to an access-   
   > controlled page on that site in your bookmarks or browser history or   
   > whatever, and it immediately sends you to the login page; after   
   > (re)entering your valid username and password, the site is nice enough to   
   > remember where you were wanting to go in the first place, and sends you   
   > back there.   
   >   
   > Are these “temporary” or “permanent” redirects?   
      
   This is not my forte', but (since) I've been reading the gglAIstuff,   
   I'll take a shot :-)   
      
   I say temporary because...   
      
   An expired cookie can trigger a temporary redirect if the redirect is   
   related to authentication or user sessions, as the server may move you   
   to a login page or another secure location after your session expires.   
      
   'Bad' cookie; temp redirect 307; straighten out the   
   cookie/authentication glitch; keep/resume heading to the original URL.   
      
   --   
   Mike Easter   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)