On Wed, Jan 30, 2013 at 06:41:07PM +1300, Amos Jeffries wrote:
On 30/01/2013 5:24 a.m., John Hay wrote:
Hi Guys,
I have been seeing this pretty often lately, with both 3.2.5 and 3.2.6.
I'm using FreeBSD 8.x in 64 bit mode and also IPv6.
The message in cache.log is:
2013/01/29 17:23:39
Hello there,
we are receiving warnings after upgrading squid from version 3.1 to 3.2 on
FreeBSD. Squid appears to be fully operational though.
The warnings seem to be relative to starting the helpers and opening the log
files, but the helpers are started and the log files written to.
# squid
On 31/01/2013 10:24 p.m., Simone Levy wrote:
Hello there,
we are receiving warnings after upgrading squid from version 3.1 to 3.2 on
FreeBSD. Squid appears to be fully operational though.
The warnings seem to be relative to starting the helpers and opening the log
files, but the helpers are
Are there any comments here? I've tried adding the following options from
http://wiki.squid-cache.org/SquidFaq/WindowsUpdate (even though I don't
especially want to cache updates)
range_offset_limit -1
maximum_object_size 200 MB
quick_abort_min -1
No joy. I've tried transparent standard proxy
Squid access logs?
What is the exact problem? you can't download at all or there is a problem?
Please share your squid.conf and squid -v output.
Where did you got your RPM? from my repo?
Please share more info and if you can get tcpdump output this can really
help to find your problem.
Note
Hello Eliezer,
Thank you for your reply. My exact problem is that Windows Updates do not
install or even download at all.
The squid RPMs were built by my partner in 2 architectures: Centos 5 i386 and
Centos 6 x86_64. Same nonfunctioning behavior in both.
I didn't realize you had a squid
Here are links to squid access.log
www.thinkwelldesigns.com/access_log.txt
And tcpdump for 10.0.2.150
www.thinkwelldesigns.com/tcpdump.zip
Thanks,
Dave
-Original Message-
From: Dave Burkholder
Sent: Thursday, January 31, 2013 10:29 AM
To: Eliezer Croitoru;
31.01.2013 18:11, Dave Burkholder:
Here are links to squid access.log
www.thinkwelldesigns.com/access_log.txt
I see nothing bad in here.
http://download.windowsupdate.com/v9/1/windowsupdate/redir/muv4wuredir.cab
link is void for some month now. It was used only for older versions of
I was able to install Eliezer's 3.2.6 RPM on one of my boxes and at this point
I find no improvement. I'm coming to the conclusion that the problem might lie
with Microsoft and this Squid upgrade of mine might be a coincidence.
For example, as Volodymyr noted, this link is down:
On 01/31/2013 03:06 AM, Amos Jeffries wrote:
On 31/01/2013 10:24 p.m., Simone Levy wrote:
Hello there,
we are receiving warnings after upgrading squid from version 3.1 to
3.2 on FreeBSD. Squid appears to be fully operational though.
The warnings seem to be relative to starting the helpers
31.01.2013 18:59, Dave Burkholder:
I was able to install Eliezer's 3.2.6 RPM on one of my boxes and at this point
I find no improvement. I'm coming to the conclusion that the problem might lie
with Microsoft and this Squid upgrade of mine might be a coincidence.
For example, as Volodymyr
Try again.
-Original Message-
From: m...@uninet.com.br [mailto:m...@uninet.com.br]
Sent: Wednesday, October 03, 2012 4:54 PM
To: squid-users@squid-cache.org
Subject: [squid-users] Squid3 reverse proxy ntlm authentication
Importance: High
I need to configure the Squid3 to authenticate
I am attempting to debug the problem I am hitting. Looking at this, I
am not sure if squid or target server doesn't like client's ssl
handshaking request. Also, I am not sure how to interpret local or
remote addresses as what says remote is the client machine that is
trying to acces the target
I'm trying to setup Squid as a reverse proxy to cache HLS segments. We
have a very controlled environment, so I'd like it to cache every .ts
file it sees, and not cache every .m3u8 file it sees. I have a pretty
generic configuration (I think) and it seems that it's not caching anything?
I don't
On 1/31/2013 6:11 PM, Dave Burkholder wrote:
Here are links to squid access.log
www.thinkwelldesigns.com/access_log.txt
Ok seems like pretty normal to me from squid point of view.
I have the same lines which windows tries to access and dosn't exist.
And tcpdump for 10.0.2.150
I have seen your logs and it seems like you have user CURL to fetch a
simple get while the clients are requesting a partial content of the
video and squid in any version dosn't cache them yet.
You can try other alternatives that can offer you this kind of feature
or reassess the way your
On 01/31/2013 01:41 PM, Eliezer Croitoru wrote:
I have seen your logs and it seems like you have user CURL to fetch a
simple get while the clients are requesting a partial content of the
video and squid in any version dosn't cache them yet.
You can try other alternatives that can offer you
Well, I'm not too familiar with tcpdump. It was tcpdump -i any host 10.0.2.150
-w tcpdump.txt
I'll be glad to remove the range_offset_limit -1 line. I'd added it because the
Squid wiki page @ http://wiki.squid-cache.org/SquidFaq/WindowsUpdate specifies
it when wanting to cache updates. I
On 1/02/2013 6:03 a.m., Alex Rousskov wrote:
On 01/31/2013 03:06 AM, Amos Jeffries wrote:
On 31/01/2013 10:24 p.m., Simone Levy wrote:
Hello there,
we are receiving warnings after upgrading squid from version 3.1 to
3.2 on FreeBSD. Squid appears to be fully operational though.
The warnings
I want to make sure that .m3u8 files are *never* cached. Those files are
updated every 5 seconds on my server, and always have the same name.
What is the best way to make sure that they are never cached? This is
what I came up with:
refresh_pattern \.m3u8 0 0% 0
Conversely, MPEG
an even better approach would be correctly setup your webserver to
send the appropriate expire times for the .m3u8 files so your caches
neither any other one would cache them :)
a correctly expire time for the .ts could be sent as well, allowing
them to be cached
Em 31/01/13
Hi,
I am just starting to test with rock. And it could be, I have just the
opposit effect: Only UFS is used, rock not, using default of 512Kb righ now.
However, will do more testing tomorrow,
but I am a bit suspicious regarding this line in your squid.conf:
maximum_object_size_in_memory 8 KB
On 1/02/2013 3:14 a.m., Teacher... wrote:
Dear Amos,
Recently we start getting and error, + auto squid restart ((( Any
suggestion? )))
You have multiple problems shown in your log. Some are easily resolved,
some are not.
Also, your Squid version is more than 5 years old. Please upgrade to
On 1/02/2013 6:32 a.m., Roman Gelfand wrote:
I am attempting to debug the problem I am hitting. Looking at this, I
am not sure if squid or target server doesn't like client's ssl
handshaking request. Also, I am not sure how to interpret local or
remote addresses as what says remote is the
Is the request or response arrives on port 80?
Thanks
From: Amos Jeffries
Sent: 1/31/2013 11:15 PM
To: squid-users@squid-cache.org
Subject: Re: [squid-users] SQUID Debugging
On 1/02/2013 6:32 a.m., Roman Gelfand wrote:
I am attempting to debug the problem I am hitting. Looking at this, I
am
On 1/02/2013 6:22 a.m., Baird, Josh wrote:
Try again.
-Original Message-
From: muno
I need to configure the Squid3 to authenticate via NTLM
reverse proxy authentication. I have instaled and configured
the squid but the browser requires the password again and
again.
Anyone have a clue
-- Forwarded message --
From: Jeff Chua jeff.chua.li...@gmail.com
Date: Fri, Feb 1, 2013 at 1:32 PM
Subject:
To: squid-users@squid-cache.org
Amos,
I'm seeing entries like these after rev 12620. It seems the -n only
applies to dst* and not src* ACL. How can I fix these?
On 1/02/2013 1:30 p.m., Leonardo Rodrigues wrote:
an even better approach would be correctly setup your webserver to
send the appropriate expire times for the .m3u8 files so your caches
neither any other one would cache them :)
+1 to that.
a correctly expire time for the .ts could be
On 1/02/2013 6:33 p.m., Jeff Chua wrote:
-- Forwarded message --
From: Jeff Chua
Amos,
I'm seeing entries like these after rev 12620. It seems the -n only
applies to dst* and not src* ACL. How can I fix these?
The no-lookup feature in 3.HEAD is unrelated to the config
29 matches
Mail list logo
