Re: Fwd: [squid-users] store-id.pl doesnt cache youtube

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Tue, 09 Jul 2013 17:06:37 +1200

On 9/07/2013 4:51 p.m., Eliezer Croitoru wrote:
> On 07/09/2013 07:32 AM, Amos Jeffries wrote:
>> On 8/07/2013 6:34 p.m., Alan wrote:
>>> On Mon, Jul 8, 2013 at 6:25 AM, Eliezer Croitoru
>>> <eliezer_at_ngtech.co.il> wrote:
>>>> try this if you want to try something new.
>>>> https://github.com/elico/squid-helpers/blob/master/squid_helpers/store-id.pl
>>>>
>>>>
>>>> Eliezer
>>> Hi Eliezer,
>>>
>>> I read your script, and I have a suggestion.
>>> How about you store the matching urls in a separate file or database?
>>> That way the script would remain the same even if some website changes
>>> their url scheme. When the squid admin wants to update the file/db he
>>> can just issue squid -k reconfigure and the script would reload the
>>> file/db.
>>>
>>> I just came up with this simple script, based on yours. I haven't
>>> tested it though, since 3.4 head segfaults for me (btw, which revision
>>> are you using?).
>>>
>>> The invocation for my script should be, for example:
>>> store_id_program /etc/squid/storeid.pl /etc/squid/storeid.txt
>>>
>>> By the way, thanks for your contributions in this mailing list, they
>>> are very helpful.
>>>
>>> Best regards,
>>>
>>> Alan
>>>
>>> PS: Had to resend to the mailing list because it doesn't allow
>>> attachments.
>>> Here are the attachments:
>>>
>>> storeid.pl script:
>>> http://pastebin.ca/2420563
>>>
>>> storeid.txt file:
>>> http://pastebin.ca/2420565
>> Nice.
>> If you would like to nominate a GPLv2 compatible license to this .pl
>> script I would be happy adding it to the Squid package.
>> I have only been rejecting the store-URL scripts earlier only because
>> they hard-coded the patterns.
>>
>> Amos
> Well Then we need to make sure the algorithm of the patterns is a bit
> more efficient.
> Then we can have the DB in wiki?? or sharing the patters between users
> can be done only on pastebin and mailing lists?

As long as it is legal I don't have any opinion on how you decide to
distribute the DB.
It is just that the source code is semi-permanent once it commits and
the patterns far too volatile for that type of publishing.

Amos
Received on Tue Jul 09 2013 - 05:06:44 MDT

This archive was generated by hypermail 2.2.0 : Tue Jul 09 2013 - 12:00:13 MDT