[squid-users] caching videos over https?

Yuri Voinov yvoinov at gmail.com
Sun Nov 20 11:32:44 UTC 2016

Yes, I do not argue. I have a solution that suits me. It is not in the
scripting language, fast and asynchronous.

As I said, if someone can find a simple solution - he would not give him
a grateful humanity. I'm happy for Kulbir If he is so good solution, as
you say. When I was two years ago, is actively studying the issue
caching Youtube, I've seen his development. It does not take much
intelligence to understand how to cache the rest of the videos - it is
only a matter of time and some effort. The biggest problem, however,
Youtube. Yes, it is possible to find a way. Someone who will do this and
give a decision - will be a valuable service to humanity. :) As I see.
If this is going to work. At this point, however, I really did not see a
complete solution that would be cached - pay attention again - Youtube
for all without exception devices, excluding Google's own solution. I
clearly express my thoughts?

20.11.2016 12:00, Garri Djavadyan пишет:
> On 2016-11-20 03:18, Yuri Voinov wrote:
>> That's why I said that the development of the Indian - fake.
> Yuri, first of all, your comment is outright _lie_ without
> justifications. Second, the developer has a name - Kulbir, and I
> believe, nationality of the developer is not relevant. Kulbir Saini,
> also wrote a book for beginners [1], directly referred on
> http://www.squid-cache.org/.
> ------
> I used the product and can confirm it worked well. The product is no
> longer actively developing and the code was moved to GitHub [2].
> Youtube support was officially dropped. Below is brief description of
> product's operations:
> 1. It adjusts refresh patterns to force video content caching,
> although the cached content could not be used by clients directly.
> 2. It continuously monitors for access.log to gather URLs and to count
> number of requests to the same URL.
> 3. The URL gets into the queue only if it was accessed configured
> number of times by a client.
> 4. It calculates exact location on the cache store for each URL and
> copies object directly from cache store to configured web server storage.
> 5. Next time, if it will detect request to already cached (on web
> server) object, URL rewriter redirects a client to the web server.
> [1] https://www.packtpub.com/squid-proxy-server-31-beginners-guide/book
> [2] https://github.com/kulbirsaini/videocache
> Garri
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users

Cats - delicious. You just do not know how to cook them.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x613DEC46.asc
Type: application/pgp-keys
Size: 2437 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20161120/51d0392d/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20161120/51d0392d/attachment.sig>

More information about the squid-users mailing list