Re: Caching URL with ?

Yuri <yvoinov@xxxxxxxxx> · Tue, 3 Oct 2017 00:14:44 +0600



    Not enough information.
    Is token persistent from GET to GET? Or it changed from day to
      day (by hash from date, for example?) If ir persistent, it can be
      stored by store-ID. If not -no.
    The other way here is not to blame. It is necessary to
      understand, whether the token is really unique for unique content
      or not. This is the subject of reverse engineering, I think.

    
    02.10.2017 23:44, Hector Chan пишет:

    
          I have a question about caching URLs with an auth token
            embedded in the URL parameter.  For example:

            
          https://www.example.com/path/page?token=xxx135ynjy93tqi
        

        The page can be uniquely identified without the URL
          parameters.  It appears squid is using the full URL, including
          the URL parameters, as the cache key.  Thus, causing the HIT
          rate to plummet.  Is there any way I can tell squid to
          disregard the URL parameters when storing to or serving from
          cache?  I know the store_id_program can do that, but is there
          any other way?
        

        Thanks,
        Hector

        
      _______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users

    
    -- 
**************************
* C++: Bug to the future *
**************************
  

Attachment:
0x3E3743A7.asc

Description: application/pgp-keys
Attachment:
signature.asc

Description: OpenPGP digital signature
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users