Hey,
So it seems pretty simple.
Your helper is very good and simple for the task and at-least we know
that if your helper works it's something with jesred 100%.
I do not know german but it's not really a big deal to understand when
you actually know how things works in general.
I do not know what settings exactly you need but you can take a look at
squid sources:
http://bazaar.launchpad.net/~squid/squid/trunk/view/head:/src/store/id_rewriters/file/storeid_file_rewrite.pl.in
Which is a very simple perl script that works with a "config" file.
It was designed to work with StoreID and some examples are at:
http://wiki.squid-cache.org/Features/StoreID/DB
But I really do not think that for a simple task such as this a special
compiled version of jesred will be much more efficient then the python
or perl scripts.
This is also since jesred doesn't implement any form of concurrency support.
I have been working on an improved compiled version(Golang) of a helper
such as the above perl one but yet to have seen a really good use case
that will benefit from that too much.
It is not 100% clear to me how the apt-cacher-ng decides which host to
fetch the requests from but if it works then it is.
All The Bests,
Eliezer
On 29/02/2016 02:34, Karl-Philipp Richter wrote:
Hi,
Am 29.02.2016 um 01:13 schrieb Eliezer Croitoru:
I do not remember if I have tried to work with such a setup in the past
but, can you give some technical details on the desired setup?
I want to manipulate URLs for Ubuntu and Debian .deb packages download
requests (usually for fixed (ftp.debian.org) or predictable URLs
([country].ubuntu.archive.com) which are passed to squid used as
intercepting HTTP cache to be served by an `apt-cacher-ng` instance.
Configuration for clients and VMs running on clients should be zero.
Are there any written documentations about such a setup already? if so can you redirect me to one of these?
Depends on your german skills:
https://forum.ubuntuusers.de/topic/squid-transparent-und-apt-cacher-ng/
Basically the jesred program as far as I remembered it was not developed for a very long time but I have found the next sources:
https://github.com/sawcache/jesred/blob/master/main.c#L166
Which indicates that someone did something with it to somehow work with Squid 3.5+ including 4.X.
If I would have known more about the setup I would probably be able to answer the question.
This still seems quite fragile, e.g. there's no automatic installation
routine (which I suggested as autconf setup in pull request
https://github.com/sawcache/jesred/pull/2). I'd like this fixed or
solved somehow to get some activity in the project as well. Otherwise
I'm not too eager to contribute since my script at
https://github.com/krichter722/apt-cacher-ng-rewriter works for now, but
isn't overly complicated and not configurable.
Also what changes in 4.X communications are you talking about?
The changes I know about are from 3.4-3.5
I was referring to probable communication changes which "might" have
been implemented - I've already made bad experience with (and filed bugs
about) outdated `squid` documentation, so I prefer to ask.
It might just be the case that `apt-cacher-ng` doesn't accept the output
of `jesred` (failure described above), but I'm wondering what could
there be wrong given the fact that my script works and this
communication protocol is no rocket science. That was the original
reason for my question/request for feedback.
-Kalle
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
