[squid-users] Which protocol uses when Stored-ID object returned by Squid?
eliezer at ngtech.co.il
Wed Aug 12 16:04:02 UTC 2015
Vimeo is using akamai and can be cached as far as I understand.
There is always an ID out there in urls(not Vimeo specific if at all in
Vimeo) but it's either encrypted or is inside the page that needs to be
These are the two options I know about and I have seen couple times that
there are something like a "cookie" url which can help to identify a
I don't remember if it was to you that I recommended Adblock plus and
video search at firefox.
There was another software which I think is called "FreeRapid
Downloader" and they have all bunch of plugins which written in java
that helped me get started on couple things with video sites analytics.
The software doesn't work very well these days but it gives a lot of
basics if you have the needed java skills(I am not pushing you to dive
into it since it's not a simple task).
Adblock plus gives you many details on every page you browse into and
have a nice filter option.
You can get into the filter and urls list using the "open blockable
items" option in the Adblock plus firefox menu.
It' much simpler then plain firefox "inspect elements" or firebug but it
is limited a bit.
* I have read people writing in forums something like "we are not spoon
feeding got read the man pages" and I do not like the attitude!!
- Also on this specific case there is not man pages or something
similar and I encourage to ask.
On 12/08/2015 17:17, Yuri Voinov wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> I still see no problem, if the same content under HTTP/HTTPS will
> deduplicated as one record.
> 12.08.15 20:06, Eliezer Croitoru пишет:
>> On 12/08/2015 16:44, Yuri Voinov wrote:
>>> Hmmmmmm. You want to say will better to have HTTP/HTTPS duplicate rules
>>> for the same content? This can lead problems with YT, for example. And
>>> make storage space bigger...
>>> Now I'm trying to produce some best practice with Store-ID for myself.
>>> This is why this question occurs.
>> I think that it's not an issue if you are bumping.
>> Youtube these days forces https whenever they can so you will probably
> won't have this issue at all.
> HSTS is not an issue - it's quite simple to disable or force URI to
> bump. Issue is still different. When rules for store id is dual - http
> and https - this occurs problems with Chrome on PC's and mobile devices.
>> Youtube is not a basic case but take a look at their smaller content
> such as youtube images which consist of one key for them all using the
> video ID which is different from vimeo and many others.
> In our country YT is basic case. This is over 80% of all video traffic.
> All others either blocked, or not know or unused. Vimeo.... Vimeo is
> great undocumented problem, like Google YT. But if YT is partially
> solved, Vimeo is completely terra incognita. :)
>> Are you looking for some sites to analyze for practice?
>> squid-users mailing list
>> squid-users at lists.squid-cache.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> -----END PGP SIGNATURE-----
> squid-users mailing list
> squid-users at lists.squid-cache.org
More information about the squid-users