Good,
that solved the problem!
Thank you
On Tue, May 7, 2013 at 6:27 PM, China wrote:
> Ok, tomorrow morning I'll try and reply!
>
> Thank again!
>
> On Tue, May 7, 2013 at 5:46 PM, Amos Jeffries wrote:
>> On 8/05/2013 3:13 a.m., China wrote:
>>>
>>> The default config restrict methods, not pro
On Tuesday, May 07, 2013 07:04:54 PM Amos Jeffries wrote:
> What Squid version were you upgrading from?
I didn't notice what version it was before.
> What user-agent / browser software are you using?
Tor Browser, which is Firefox long-term release. I switch between Squid and
Tor with
I figured out what I was doing wrong. I was running squid2 and upgraded to
squid3.3.3. Squid3 was installed in the /etc/squid3 directory which is
different than the previous /etc/squid. I needed to modify
/etc/squid3/squid.conf configuration. The setting request_header_add is
working now. Than
On 8/05/2013 11:24 a.m., frodie123 wrote:
Norman...I am testing squid3.3.3 running on Ubuntu and using the
request_header_add setting but it is not working for me. I am just testing
HTTP only, no HTTPS. I tried both of these settings:
acl allip src 0.0.0.0/0.0.0.0
request_header_add X-YouTube-
On 8/05/2013 4:36 a.m., cac...@quantum-sci.com wrote:
Squid 3.3.3-2 on Debian Testing. Suddenly today after a dist-upgrade
yesterday, I am getting a plague of:
Content Encoding Error
The page you are trying to view cannot be shown because it uses an
invalid or unsupported form o
Norman...I am testing squid3.3.3 running on Ubuntu and using the
request_header_add setting but it is not working for me. I am just testing
HTTP only, no HTTPS. I tried both of these settings:
acl allip src 0.0.0.0/0.0.0.0
request_header_add X-YouTube-Edu-Filter "abc123" allip
and also,
reques
Squid 3.3.3-2 on Debian Testing. Suddenly today after a dist-upgrade
yesterday, I am getting a plague of:
Content Encoding Error
The page you are trying to view cannot be shown because it uses an
invalid or unsupported form of compression.
This is intolerable. Does anyone know th
Ok, tomorrow morning I'll try and reply!
Thank again!
On Tue, May 7, 2013 at 5:46 PM, Amos Jeffries wrote:
> On 8/05/2013 3:13 a.m., China wrote:
>>
>> The default config restrict methods, not protocol.
>>
>> The problem can be translated as: what I've to put in 'acl
>> allowed_protocols proto .
On 05/07/2013 09:49 AM, Martin Sperl wrote:
> Is there any other configuration option (in squid 3.2) to log if an
> ACL matches in the access-log? (which is all I essentially need)
I have listed all the options I could think of, but I missed the
"different logformat" options you mentioned. I thin
Yes, I am EXACTLY talking about this...
Or a means to log if an ACL matches of not in true/false (or maybe via notes,
which are not fully documented yet on the website).
But then Trunk is definitely not ready for a production envirionment...
So if you can think of something else that may get me
On 8/05/2013 2:03 a.m., Martin Sperl wrote:
Hi!
I have configured squid 3.2.7 logging with the following pattern to log:
logformat xml ...%{Via}>ha...
access_log daemon:/var/logs/squid/access_log.xml xml all
But I have the problem, that the fields stay "empty" (actually "-")...
So I wonder w
Hi Alex!
Is there any other configuration option (in squid 3.2) to log if an ACL matches
in the access-log? (which is all I essentially need) (besides logging to 2
different logfiles - been there and there was this issue with multiple
instances of the logger daemon writing to the same file)
Ev
On 8/05/2013 3:13 a.m., China wrote:
The default config restrict methods, not protocol.
The problem can be translated as: what I've to put in 'acl
allowed_protocols proto ...' to permit https traffic with CONNECT
method?
Try "NONE". CONNECT URLs have no protocol scheme, just a TCP IP:port (or
On 05/07/2013 08:03 AM, Martin Sperl wrote:
> I have configured squid 3.2.7 logging with the following pattern to log:
>
> logformat xml ...%{Via}>ha...
> access_log daemon:/var/logs/squid/access_log.xml xml all
>
> But I have the problem, that the fields stay "empty" (actually "-")...
>
> So
OK, I have done some more testing:
if I send A Via Header, then this header gets logged with "%{Via}>h" - but ONLY
the value sent (not the modified version)
if I log instead the response header with %{Via}%{Via}>ha...
access_log daemon:/var/logs/squid/access_log.xml xml all
But I have the probl
The default config restrict methods, not protocol.
The problem can be translated as: what I've to put in 'acl
allowed_protocols proto ...' to permit https traffic with CONNECT
method?
If I start Squid in debugging mode this is the trace with problems:
kid1| Eui48.cc(262) lookup: Looking up ARP
Many thanks
I'll try --disable-strict-error-checking first to see if it gets me up and
running.
I'm working to quite a tight schedule but if I get time I'll try and run it
against the HEAD and feed back a list any of errors I find.
--
View this message in context:
http://squid-web-proxy-c
On 8/05/2013 1:31 a.m., China wrote:
Hi,
I've some squid servers (until 3.1.20 version) which has the following
configuration and works great:
acl allowed_protocols proto HTTP HTTPS CONNECT FTP
http_access deny !allowed_protocols
After the upgrade to 3.3.3 version, sqiud print the following
On 8/05/2013 1:12 a.m., Mr J Potter wrote:
Hi Pablo,
Yes, http and https traffic all go through squid, which listens on
port 3128. Clients are configured to use this with a PAC file. The
HTTPS requests show up as CONNECT requests, which all work fine. I
just see no entries when I'm sure AJAX com
On 8/05/2013 1:32 a.m., C. Pelissier wrote:
Use Solaris gcc (compiling with studio no longer works after version
2.7).
It should. We had 3.1 building with Studio before the public build farm
we were using to maintain the portability got discontinued. Now we are
back once again reliant on peop
Hi!
I have configured squid 3.2.7 logging with the following pattern to log:
logformat xml ...%{Via}>ha...
access_log daemon:/var/logs/squid/access_log.xml xml all
But I have the problem, that the fields stay "empty" (actually "-")...
So I wonder why and how I can change that, so that I get th
Use Solaris gcc (compiling with studio no longer works after version
2.7).
Le mar. 07/05/2013 à 15:08, drewB a écrit :
> Compiling version 3.3.4 on Solaris 10 using Solaris Studio 12.3, I get the
> following error:
>
> ...
> Making all in format
> source='Config.cc' object='Config.lo' libtool=ye
Hi,
I've some squid servers (until 3.1.20 version) which has the following
configuration and works great:
acl allowed_protocols proto HTTP HTTPS CONNECT FTP
http_access deny !allowed_protocols
After the upgrade to 3.3.3 version, sqiud print the following warning
in the configuration check:
WA
Hi Pablo,
Yes, http and https traffic all go through squid, which listens on
port 3128. Clients are configured to use this with a PAC file. The
HTTPS requests show up as CONNECT requests, which all work fine. I
just see no entries when I'm sure AJAX communications are going on.
These must be going
Compiling version 3.3.4 on Solaris 10 using Solaris Studio 12.3, I get the
following error:
...
Making all in format
source='Config.cc' object='Config.lo' libtool=yes \
DEPDIR=.deps depmode=none /bin/bash ../../cfgaux/depcomp \
/bin/bash ../../libtool --tag=CXX--mode=compile CC -DHAVE_CONFIG_H
Hi, Google services use the HTTPS port, your SQUID is configured to
listen on that port?
2013/5/7 Mr J Potter :
> Hi all,
>
> I'm having a problem with filtering user access specifically with
> Google (Mail, docs, calendars etc) - it looks to me like not all the
> requests the client makes are sho
Hi all,
I'm having a problem with filtering user access specifically with
Google (Mail, docs, calendars etc) - it looks to me like not all the
requests the client makes are showing up in squid access log.
As far as I can tell, AJAX requests aren't logged, and I know google
are big AJAX fans, so I
More info
[root@proxyprueba ~]# /usr/lib64/squid/squid_kerb_auth_test -d -s
HTTP/proxyprueba.abg.c...@abg.corp
Token:
YIIFdgYGKwYBBQUCoIIFajCCBWagCjAIBgYrBgEFAgWiggVWBIIFUmCCBU4GBisGAQUCBQUBMAyhCgQIQUJHLkNPUlBsggUyMIIFLqEDAgEFogMCAQyjggTOMIIEyjCCBMahAwIBAaKCBL0EggS5boIEtTCCBLGgAwIBBaEDAgEOogcDBQAA
Hi Amos,
This patch (to 3.3.2) is still missing (which you had sent
for wrong logging of IPv6 address instead of IPv4)
--- squid-3.3.2/src/forward.cc 2013-02-25 03:42:35 +
+++ squid-3.3.2/src/forward.cc 2013-03-07 07:38:16 +
@@ -984,6 +984,7 @@
serverConn->peerType = H
Thanks for the hint - we already have got quite an elaborate db-logging
mechanism which reads from the logfiles (as in 3.0 squid did only allow logging
to file).
And as we need to go live soon, I want to avoid starting with a last-minute
changes to the logging...
So I will have to "redesign" th
A lot of thanks Markus and sorry by my big delay in answering but I didn't
know suficient for reply you.
I read a lot of posts and I checked my configuration and I think that now I
can reply you.
My configuration
[logging]
default = FILE:/var/log/krb/krb5libs.log
kdc = FILE:/var/log/krb/krb5kdc.
31 matches
Mail list logo
