Sure, anything's possible. Create a shell script in /etc/init.d that starts squid with a different config file. Create packet filter rules to descriminate internal HTTP packets vs those arriving on the external interface. And... voila! Easier said than done I'm sure, but these are the steps in broad strokes.
hacking the asl is not a real solution for me. after the next update all scripts are overwritten. the squid proxy is a part of asl 4 and 5. the question is why astaro don't impelment this feature.
i'm verry interested to solve the problem with an official solution. an statement from the astaro team is most welcome.
rally it is not needed..besides ASL is trying to avoid feature creep and trying to keep ASL from becoming like many firewalls out there that either require dedicated hardare or high powered hardware to run....my feelings on this issue are detailed in another thread started by the same person who started this one: https://community.sophos.com/products/unified-threat-management/astaroorg/f/56/t/49106
if you dont need the feature - dont use the feature! other users need some features u dont need. if you not use the feature you dont need better hardware.
[ QUOTE ] if you dont need the feature - dont use the feature! other users need some features u dont need. if you not use the feature you dont need better hardware.
greetings
[/ QUOTE ]
newer unused features still require mode codespace and hence at least more drive space..I agree with Gert as well this is not able to be done as i mentioned before they have set the deadline(hence limiting feature creep which leads to delays)...reverse proxies are nice but not really needed inside astaro..if you need the reverse proxies setup the reverse proxy box behind astaro..setup a DMZ for the proxy then put your web servers behind it....good to go..[:)]
