It is but it’s the latest version available through apt-get on Debian 7 without
adding backports which I may end up doing anyway. However I don’t think that is
my problem, I think I may have missed something in my config and was wondering
if anyone had seen this before with the usernames not see
On 27/01/2015 11:33 p.m., Josep Borrell wrote:
> I agree.
> Are there someone with the skills to help us with a working sample ?
> is an external ACL needed as Dan remarks ?
> maybe the peek and splice feature need some tuning ?
> if I can help with something, tell me.
>
I've sent a virtual poke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hmm.. Why so ancient Squid version?
3.1.x is legacy.
Now Amos says: "Upgrade to last version". ;)
Which is 3.5.1 (wow! :))
28.01.2015 3:48, Bobby пишет:
>
> Sorry if you’re seeing this twice… I think I sent it to the wrong
address the fir
Sorry if you’re seeing this twice… I think I sent it to the wrong address the
first time.
Hello,
Ive been using squid + dansguardian (NTLM) for a few years now
and have begun setting up a new proxy with squid 3.1.20. Everything
seems to be working fine except I don’t seem to be sending the
On 28/01/2015 7:04 p.m., Ahmad wrote:
> Hi mates ,
>
>
>
> I have a proxy provider that give me may sessions , and each session is per
> username and pwd.
>
> As an example , I have the provider 1.1.1.1 with 5 usernames
>
> Each username will give me different ip.
>
>
>
> I need to do on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yep :)
"test received, TTL=34 min" :)
28.01.2015 3:41, Ambrose LI пишет:
> I thought the correct answer to "test" would be "test received".
> "Pong" would be correct only if the test message was "ping". No? :-)
>
> On 27 January 2015 at 16:26, Shen
On 28/01/2015 7:10 p.m., Ahmad wrote:
> Hi dev ,
>
> how long object size can squid 3.5.2 handle ??
>
> it says >>than 32KB
>
What "it" ?
>
> is that for memory or disk caching or for both
>
SMP memory is the only one restricted to 32KB. Because 32KB is the
default UDS (Unix Data So
I thought the correct answer to "test" would be "test received".
"Pong" would be correct only if the test message was "ping". No? :-)
On 27 January 2015 at 16:26, Shenan Hawkins wrote:
> 1422375352.851 42 127.0.0.1 JOKE_MISS/206 1d0n7 GET http://it
>
> On 27 January 2015 at 16:13, Yuri Voinov wr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm waiting for working transparent interception bumping ;)
yet sit on 3.4.11 ;)
28.01.2015 3:30, Amos Jeffries пишет:
> On 28/01/2015 9:29 a.m., Yuri Voinov wrote:
>
> > In 3.5.2? :) It already released? :)
>
> Aye, if that was meant to say 3.5.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/01/2015 9:29 a.m., Yuri Voinov wrote:
>
> In 3.5.2? :) It already released? :)
Aye, if that was meant to say 3.5.0.2 (the beta) - then please upgrade
Urgently to current stable.
Amos
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW
On 28/01/2015 2:44 a.m., masterx81 wrote:
> I'll doubt is a chrome bug, as with direct connection i've not any problem...
>
Lets see,
* Chrome, fail
* Firefox, works via Squid
* MSIE, works via Squid
* test tool, works via Squid
There is also the factum that direct non-proxied connections do
1422375352.851 42 127.0.0.1 JOKE_MISS/206 1d0n7 GET http://it
On 27 January 2015 at 16:13, Yuri Voinov wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Amos,
>
> the better answer is "pong" ;) And don't forget to add TTL ;)
>
> 28.01.2015 3:01, Amos Jeffries пишет:
> > On 28/01/201
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amos,
the better answer is "pong" ;) And don't forget to add TTL ;)
28.01.2015 3:01, Amos Jeffries пишет:
> On 28/01/2015 6:54 p.m., Ahmad wrote:
>> testt
>>
>
> Ping. This got through.
>
> Amos
>
> _
I might have found something
Turning up debugging shows that squid is learning the SNI value from an
intercepted/transparent HTTPS session (or is it learnt from the server
response?)
2015/01/28 09:23:34.328 kid1| bio.cc(835) parseV3Hello: Found server
name: www.kiwibank.co.nz
Looking that up in
On 28/01/2015 6:54 p.m., Ahmad wrote:
> testt
>
Ping. This got through.
Amos
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In 3.5.2? :) It already released? :)
But really - with 64 bit build with enough RAM under 64 bit OS on 64 bit
(or 128 bit) filesystem you can save as big object your want with any
Squid. :)
28.01.2015 12:10, Ahmad пишет:
>
> Hi dev ,
>
> how long
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In 3.5.2? :) It already released? :)
But really - with 64 bit build with enough RAM under 64 bit OS on 64 bit
(or 128 bit) filesystem you can save as big object your want with any
Squid. :)
28.01.2015 12:10, Ahmad пишет:
-BEGIN PGP SIGNATURE
Hi dev ,
how long object size can squid 3.5.2 handle ??
it says >>than 32KB
is that for memory or disk caching or for both
I mean does that mean on memory the hot object will be >>32KB ?
And in rock store >>32 also ?
If >>32 Kb how much ?
500 Kb ? 1M or more or les
On 27/01/15 11:13, Dan Charlesworth wrote:
> Wasn't somebody saying that you'd need write an External ACL to
> evaluate the SNI host because dstdomain isn't hooked into that code
> (yet? ever?)?
That can't be the case. If the external ACL is called without the SNI,
then at best all it can do is co
Hi mates ,
I have a proxy provider that give me may sessions , and each session is per
username and pwd.
As an example , I have the provider 1.1.1.1 with 5 usernames
Each username will give me different ip.
I need to do on my proxy something like cache peer to the ip 1.1.1.1 and
need to s
testt
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
Hello,
I thought I would make everyone on this list aware of an issue between
squid 3.4.x (and perhaps 3.5?) and FreeBSD 10.1-RELEASE. There was a
regression in the FreeBSD 10.1-RELEASE kernel's signal handling behavior
that causes squid to coredump and restart itself when receiving the
shutdown s
I'll doubt is a chrome bug, as with direct connection i've not any problem...
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-and-site-ryanair-com-tp4669105p4669366.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
Upon squid -k parse, I get a segmentation fault/coredump.
FreeBSD banter 10.1-RELEASE FreeBSD 10.1-RELEASE #0: Sat Jan 24 09:09:29
EAT 2015 root@banter:/usr/obj/usr/src/sys/BEASTIE-10.x amd64
root@mail:/opt/squid-3.5.0.4 # ./sbin/squid -v
Squid Cache: Version 3.5.0.4
Service Name: squid
con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
131 error means:
CONNECTED(0003)
write:errno=131
- ---
no peer certificate available
- ---
No client certificate CA names sent
- ---
SSL handshake has read 0 bytes and written 148 bytes
- ---
New, (NONE), Cipher is (NONE)
Looks like something i
I agree.
Are there someone with the skills to help us with a working sample ?
is an external ACL needed as Dan remarks ?
maybe the peek and splice feature need some tuning ?
if I can help with something, tell me.
Josep
De: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] En nombre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Exist:
http://i.imgur.com/JJAkR0x.png
And I am not a clue.
27.01.2015 16:23, Amos Jeffries пишет:
> not a clue.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBAgAGBQJUx2f2AAoJENNXIZxhPexG/O0H/0hKC9X3ejf0sFAKbrdR9fRB
BGAXsrArs+t9fpwXKR8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/01/2015 10:59 p.m., Yuri Voinov wrote:
>
> Squid 3.4.11. Translation enabled. All error pages and directories
> exists.
>
> But sometimes:
>
> 2015/01/27 15:56:48 kid1| WARNING: Error Pages Missing Language:
> en-gb 2015/01/27 15:56:48 kid1| W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Squid 3.4.11. Translation enabled. All error pages and directories exists.
But sometimes:
2015/01/27 15:56:48 kid1| WARNING: Error Pages Missing Language: en-gb
2015/01/27 15:56:48 kid1| WARNING: Error Pages Missing Language: en
Why?
-BEGIN P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oh, shi..
It can't be on proxy host or other infrastructure. It can be on these
client..
Let's check.
27.01.2015 10:41, Amos Jeffries пишет:
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBAgAGBQJUx1jpAAoJENNXIZxhPexG24YIAL1ncl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oh, shi..
It can't be on proxy host or other infrastructure. It can be on these
client..
Let's check.
27.01.2015 10:41, Amos Jeffries пишет:
> On 27/01/2015 11:13 a.m., Yuri Voinov wrote:
>
> > -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/01/2015 8:16 a.m., Yuri Voinov wrote:
>
> No one ssl_bump combination did not work.
>
> With your config I see only:
>
> 1422299531.482 18722 192.168.100.5 TCP_TUNNEL/200 99418 CONNECT
> 128.121.22.133: 443 - ORIGINAL_DST/128.121.22.133 -
>
32 matches
Mail list logo
