On 03/10/17 06:44, Hector Chan wrote:
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 ful
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
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 th