[squid-users] Is jesred still compatible with squid 4.x?

[Karl-Philipp Richter]

Am 26.02.2016 um 16:20 schrieb Karl-Philipp Richter:
> I noticed that `jesred` when used as `url_rewrite_program` program of
> `squid` 4.0.4 with `jesred.rules`
> 
>     regex ^http://(de.archive.ubuntu.com/ubuntu/(dists|pool)/.*)$
> http://192.168.178.20:3142/\1
>     regex ^http://(security.ubuntu.com/ubuntu/(dists|pool)/.*)$
> http://192.168.178.20:3142/\1
>     regex ^http://(extras.ubuntu.com/ubuntu/(dists|pool)/.*)$
> http://192.168.178.20:3142/\1
>     regex ^http://(archive.canonical.com/ubuntu/(dists|pool)/.*)$
> http://192.168.178.20:3142/\1
> 
>     regex ^http://(packages.medibuntu.org/(dists|pool)/.*)$
> http://192.168.178.20:3142/\1
>     regex
> ^http://(ppa.launchpad.net/chromium-daily/stable/ubuntu/(dists|pool)/.*)$ http://192.168.178.20:3142/\1
>     regex ^http://(http://deb.opera.com/opera/(dists|pool)/.*)$
> http://192.168.178.20:3142/\1
> 
> and an instance of `apt-cacher-ng` running on `192.168.178.20:3142`
> (according to `netstat`) causes a lot of entries like
> 
>     1456494043|E|481|192.168.178.20|403 Forbidden file type or location:
> /security.ubuntu.com/ubuntu/dists/wily-proposed/main/binary-i386/Packages.gz192.168.179.2/192.168.179.2-GET
After writing my own `url_rewrite_program` script I'd say that `jesred`
no longer is compatible with at least `apt-cacher-ng`. I don't know
about `squid` since rewriting can cause all sort of trouble.

-Kalle