Hi All,
Some time ago we ran into a problem with a specific website. The webserver
reported a 404 error at a .js scripting page. It was not likely the problem
was at the website (accessing the same page from behind a clean internet
connection (no Proxy/firewall/eSafe) the website was working as it supposed
to be).
I asked the administrators at the website to investigate the websites
access-log for unusual activity coming from our IP address. They pointed
out to me that there's a compatibility problem with our proxy.
Now some while later, I looked into some eSafe documentation and found out
there's an attribute: http_force_down_to_10 which proparbly could solve
this problem. I'm not sure about this one, so I have to test it in the live
environment because we have no test environment.
Before implementing this, I would like to know what changes in HTTP
activity I can expect.
So I hope someone can tell me the difference between HTTP 1.0 and HTTP 1.1
and the implications of 'forcing down' the fw to HTTP 1.0.
Thanks,
--Jan.
--
_____________________________________________________________________
2x sneller ADSL met Zon Breedband Family. In combinatie met ZonTel
nu voor maar 29 euro per maand. Bestel nu op www.zonnet.nl/breedband
Bovendien met gratis modem en geen aansluitkosten!
=================================================
To set vacation, Out-Of-Office, or away messages,
send an email to LISTSERV AT amadeus.us.checkpoint DOT com
in the BODY of the email add:
set fw-1-mailinglist nomail
=================================================
To unsubscribe from this mailing list,
please see the instructions at
http://www.checkpoint.com/services/mailing.html
=================================================
If you have any questions on how to change your
subscription options, email
fw-1-owner AT ts.checkpoint DOT com
=================================================
|
