From: ldo@nz.invalid   
      
   On 16 Aug 2025 20:13:03 -0300, Mike Spencer wrote:   
      
   > There's a work-around that can help a little for site you visit often,   
   > assuming that useful info will render w/o js, assuming you have a   
   > resident web server on localhost and can write some perl code.   
      
   In other words, create your own web-caching server. There is already   
   existing Free software (e.g. Squid) that does more along those lines than   
   you might be able to think of.   
      
   Back in my dialup days, I discovered one day, quite by accident, that my   
   ISP was proxying my port-80 accesses☛ through its own web cache. I   
   discovered this when I was working on a client’s site, and was baffled to   
   find that my changes were not being picked up on a refresh.   
      
   I can’t remember what I did for a workaround: it might have been as simple   
   as configuring Apache to listen on an additional nonstandard port, that I   
   used only for testing.   
      
   ☛Remember, this was when people had to pay for TLS/SSL certs, so they were   
   much less common   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)