|
From: Olivier B. <Oli...@pu...> - 2005-04-20 10:28:06
|
Hello,
On Tue, Apr 19, 2005 at 06:05:20PM +0200, Olivier Bornet wrote:
> since Monday, we have a new firewall at work. And since Monday, we have
> problems with apt-proxy. And it seems the problem is related to this new
> firewall.
I have found a work-around for my problem by patching apt_proxy.py. I
don't know if this is a valid correction or not, but with this
correction, all seems to be OK.
The patch add the hostname and port to the sendCommand(), even if we
don't go trough a proxy...
Anyway, this seem to be a problem with our "new" firewall. It seems to
block simple session like:
telnet the-outside-web-server 80
GET /
You need to do at least:
telnet the-outside-web-server 80
GET / HTTP/1.0
Host: the-outside-web-server
You can also make:
telnet the-outside-web-server 80
GET http://the-outside-web-server/
Don't know if this filtering by the firewall is some kind of
"security rule", or if this is not a correct HTTP protocol to say only
"GET /".
Thanks to look at the attached patch, and let me know if this is a
correct patch or not.
Good day.
Olivier
--
Olivier Bornet | français : http://puck.ch/f
Swiss Ice Hockey Results | english : http://puck.ch/e
http://puck.ch/ | deutsch : http://puck.ch/g
Oli...@pu... | italiano : http://puck.ch/i
Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/
|