Adam@Gmail schrieb:
Hi there,
Thanks for your reply, I was merely asking if anyone has or had the
same problem before, or anyone who might have a solution, of course
and you got a quick answer... answering time might beat most expensive
support services for commercial software . :-))
If I stop squid now and disable it reconfigure my system to what it
was before of course I will get the updates and the access to the
internet
but now any application or programme I want to run I have to find out
where it is where it's going etc..
It looks as if I need to tweak for every single task,. of every single
application of every single client.
Yes I have followed the configuration where the whole internet goes
through a proxy, when faced with a problem like this can you
imagine how many programmes and apps are there? If I have to tweak
each and everyone of them by hand and how many clients I have and so on
So I can spend the rest of my life fixing things.
Ah, well in the effect the http_proxy variable is not special to
apt-get , almost all (I don't recall an exception) unix command line
programs in different distributions obey this variable, also many
programming language libraries. Examples are yum, wget, java ...
So if you set these two variables in a general shell option file, you
should be done for most cases.
But there is also a different solution to this problem. You can use
squid to do transparent proxying, that is, intercept outgoing requests
on port 80 (instead of 8080, 3128 etc) and redirect them to the origin
servers. With a setup in this way, all applications work without proxy
settings as they never know they are talking to a proxy. Instructions
for setup can be found in the squid wiki and in many howtos out there.
But beware! This setup has other disadvantages. Before deploying such a
setup - in fact, before deploying any proxy setup in a production
enviroment - you should thoroughly test this with an environment where
failures are not critical.
Regards,
Jakob Curdes
