March 29, 2009 14:08
Subject: Re: [squid-users] Squid, Symantec LiveUpdate, and HTTP 1.1 versus
HTTP 1.0
Wong wrote:
Wong wrote:
I found that Symantec LU has round robin DNS. And they can change DNS
A
record at anytime.
Isn't it better if Squid can bypass the domain name in squid.conf
Wong wrote:
Wong wrote:
I found that Symantec LU has round robin DNS. And they can change
DNS A
record at anytime.
Isn't it better if Squid can bypass the domain name in squid.conf?
Is it possible?
Squid does many DNS things and has many controls for changing how it
does them.
Correct use
Amos Jeffries wrote:
Wong wrote:
I found that Symantec LU has round robin DNS. And they can change DNS
A
record at anytime.
Isn't it better if Squid can bypass the domain name in squid.conf?
Is it possible?
Squid does many DNS things and has many controls for changing how it
does them.
Co
Wong wrote:
I found that Symantec LU has round robin DNS. And they can change DNS A
record at anytime.
Isn't it better if Squid can bypass the domain name in squid.conf?
Is it possible?
Squid does many DNS things and has many controls for changing how it
does them.
Correct use of DNS in sta
Amos Jeffries wrote:
Wong wrote:
I found that Symantec LU has round robin DNS. And they can change DNS A
record at anytime.
Isn't it better if Squid can bypass the domain name in squid.conf?
Is it possible?
Squid does many DNS things and has many controls for changing how it
does them.
Cor
Wong wrote:
I found that Symantec LU has round robin DNS. And they can change DNS A
record at anytime.
Isn't it better if Squid can bypass the domain name in squid.conf?
Is it possible?
Squid does many DNS things and has many controls for changing how it
does them.
Correct use of DNS in sta
Wong wrote:
I found that Symantec LU has round robin DNS. And they can change DNS A
record at anytime.
Isn't it better if Squid can bypass the domain name in squid.conf?
Is it possible?
Squid does many DNS things and has many controls for changing how it
does them.
Correct use of DNS in sta
I found that Symantec LU has round robin DNS. And they can change DNS A
record at anytime.
Isn't it better if Squid can bypass the domain name in squid.conf?
Is it possible?
Squid does many DNS things and has many controls for changing how it does
them.
Correct use of DNS in stateless HTTP s
I found that Symantec LU has round robin DNS. And they can change DNS A
record at anytime.
Isn't it better if Squid can bypass the domain name in squid.conf?
Is it possible?
Squid does many DNS things and has many controls for changing how it does
them.
Correct use of DNS in stateless HTTP s
line but email me if you are stuck.
Cheers,
Pieter
- Original Message -
From: "Wong"
To: "Marcus Kool"
Cc: "Squid-users"
Sent: Friday, March 27, 2009 7:40 PM
Subject: Re: [squid-users] Squid, Symantec LiveUpdate, and HTTP 1.1 versus
HTTP 1.0
Dear all,
Wong wrote:
Dear all,
I found that Symantec LU has round robin DNS. And they can change DNS A
record at anytime.
Isn't it better if Squid can bypass the domain name in squid.conf?
Is it possible?
Squid does many DNS things and has many controls for changing how it
does them.
Correct use of
ssage -
From: "Marcus Kool"
To: "Nathan Eady"
Cc:
Sent: Thursday, March 26, 2009 04:09
Subject: Re: [squid-users] Squid, Symantec LiveUpdate, and HTTP 1.1 versus
HTTP 1.0
The story about Squid and HTTP 1.1 is long...
To get your LiveUpdate working ASAP you migh
Nathan Eady wrote:
Marcus Kool writes:
The story about Squid and HTTP 1.1 is long...
Holy cow, it would have to be. Squid is barely even older than HTTP 1.1.
To get your LiveUpdate working ASAP you might want to
fiddle with the firewall rules and to NOT redirect
port 80 traffic of Symantec
Marcus Kool writes:
> The story about Squid and HTTP 1.1 is long...
Holy cow, it would have to be. Squid is barely even older than HTTP 1.1.
> To get your LiveUpdate working ASAP you might want to
> fiddle with the firewall rules and to NOT redirect
> port 80 traffic of Symantec servers to Squi
Gavin McCullagh wrote:
Hi,
On Thu, 26 Mar 2009, Amos Jeffries wrote:
A very few. Pressure is on them to fix up when they break so it's no
common fortunately.
Phew. I guess if we needed to I can alter our wpad.dat and policy filter
to dictate direct access to norton updates, though I'd real
Hi,
On Thu, 26 Mar 2009, Amos Jeffries wrote:
> A very few. Pressure is on them to fix up when they break so it's no
> common fortunately.
Phew. I guess if we needed to I can alter our wpad.dat and policy filter
to dictate direct access to norton updates, though I'd really rather not.
I do se
Gavin McCullagh wrote:
Hi,
On Wed, 25 Mar 2009, Marcus Kool wrote:
The story about Squid and HTTP 1.1 is long...
To get your LiveUpdate working ASAP you might want to
fiddle with the firewall rules and to NOT redirect
port 80 traffic of Symantec servers to Squid, but
simply let the traffic pa
Hi,
On Wed, 25 Mar 2009, Marcus Kool wrote:
> The story about Squid and HTTP 1.1 is long...
>
> To get your LiveUpdate working ASAP you might want to
> fiddle with the firewall rules and to NOT redirect
> port 80 traffic of Symantec servers to Squid, but
> simply let the traffic pass.
We're runn
The story about Squid and HTTP 1.1 is long...
To get your LiveUpdate working ASAP you might want to
fiddle with the firewall rules and to NOT redirect
port 80 traffic of Symantec servers to Squid, but
simply let the traffic pass.
Nathan Eady wrote:
Okay, we've got port 80 traffic going transpar
Okay, we've got port 80 traffic going transparently to a Squid proxy
here, and I need to make a small configuration change, and I can't
seem to find, either in the man pages nor on the web, the
documentation on how to do it. It's probably one little line in
squid.conf, but I can't find it.
Here's
20 matches
Mail list logo
