On 20/02/11 18:05, Mohamed Adhil wrote:
Dear ,
I am getting following error on my squid box
ERROR
The requested URL could not be retrieved
While trying to retrieve the URL: http://www.google.com/
The following error was encountered:
* Read Error
The system returned:
(104) Connection reset
well i implemented the deicated squid 2.7 server and ti works fine.
it took me awhile to understand how the squid peering system works.
what i did was to deny all icp-htcp features and also denied direct
access to youtube on the main cache server
and i added the cache peer for the youtube
Hi my name is Shawn Caron I am havving issues with the new squid
3.1.11. I cant get my laptop to download any updates from with in squid
3.1.11. I have digest auth installed working correctly for web browsers
only. But when i try to update the laptop through aptitude using a sh
script i cant get
On Sun, 20 Feb 2011 11:57:28 -0500, Shawn wrote:
Hi my name is Shawn Caron I am havving issues with the new squid
3.1.11. I cant get my laptop to download any updates from with in
squid
3.1.11. I have digest auth installed working correctly for web
browsers
only. But when i try to update the
Hi Guys,
I run a reverse proxy for a client. They are using XFF for restricting
certain content to IP.
We have noted that the following doesn't appear to work as it should:
header_replace X-Forwarded-For allow all
My understanding is that this will cause squid to replace the XFF header
On Mon, 21 Feb 2011 12:16:46 +1300 (NZDT), Pieter De Wit wrote:
Hi Guys,
I run a reverse proxy for a client. They are using XFF for
restricting certain content to IP.
We have noted that the following doesn't appear to work as it
should:
header_replace X-Forwarded-For allow all
My
Hi Amos,
Thanks for the reply - I remember seeing the doc bug :)
I am building the Deb6 boxes as we speak (ext4+squid 3.1 is sounding very
nice)
Cheers,
Pieter
On Mon, 21 Feb 2011, Amos Jeffries wrote:
On Mon, 21 Feb 2011 12:16:46 +1300 (NZDT), Pieter De Wit wrote:
Hi Guys,
I run a
Hi Amos,
just had a go at this:
request_header_access X-Forwarded-For deny
header_replace X-Forwarded-For
and it's still passing XFF from another source thru - Nothing to urgent
since the Deb6 boxes are getting built :) But if you spot something ?
Cheers,
Pieter
On 21/02/11 16:33, Pieter De Wit wrote:
Hi Amos,
just had a go at this:
request_header_access X-Forwarded-For deny
header_replace X-Forwarded-For
and it's still passing XFF from another source thru - Nothing to urgent
since the Deb6 boxes are getting built :) But if you spot something ?
Hi,
Can anyone point me to a right direction on how to resolve this problem? I
have this on my cache manager,
FQDN Cache Statistics:
FQDNcache Entries: 3
FQDNcache Requests: 2095916
FQDNcache Hits: 0
FQDNcache Negative Hits: 0
FQDNcache Misses: 2095916
FQDN Cache Contents:
IP Cache
Hi
Is my scenario in general possible to implement (connect directly, if
the one and only cache_peer fails)?
Thanks a lot.
Tom
2011/2/17 Tom Tux tomtu...@gmail.com:
Hi Amos
This doesn't work as expected. I removed the never_direct entry (I
was unsure, how strong it is in the
Hi there,
I've been trying to do the same thing, but squid always tries too hard
on parents.
You can do this as what I do:
Have a local squid with always_direct allow all listening on another
port as the last entry of cache_peer with a default .
when squid tried the peers above and failed, it
On 21/02/2011 18:16, Amos Jeffries wrote:
On 21/02/11 16:33, Pieter De Wit wrote:
Hi Amos,
just had a go at this:
request_header_access X-Forwarded-For deny
header_replace X-Forwarded-For
and it's still passing XFF from another source thru - Nothing to urgent
since the Deb6 boxes are getting
13 matches
Mail list logo
