<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Not enough information.</p>
<p>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.</p>
<p>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.<br>
</p>
<br>
<div class="moz-cite-prefix">02.10.2017 23:44, Hector Chan пишет:<br>
</div>
<blockquote type="cite"
cite="mid:CAEhCwUw-0N3Qdyc6Hj5t2fcTj90UW13tC-QZN9vNmZa57S9GLw@mail.gmail.com">
<div dir="ltr">
<div>
<div>I have a question about caching URLs with an auth token
embedded in the URL parameter. For example:<br>
<br>
</div>
<a
href="https://www.example.com/path/page?token=xxx135ynjy93tqi"
moz-do-not-send="true">https://www.example.com/path/page?token=xxx135ynjy93tqi</a></div>
<div><br>
</div>
<div>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?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Hector<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
squid-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a>
<a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
**************************
* C++: Bug to the future *
**************************</pre>
</body>
</html>