On Fri, Nov 17, 2017 at 3:53 AM, Amos Jeffries wrote:
> On 17/11/17 03:49, Bike dernikov1 wrote:
>>
>> On Thu, Nov 16, 2017 at 8:58 AM, Amos Jeffries wrote:
>>>
>>> On 16/11/17 01:32, Bike dernikov1 wrote:
If i can ask under same title:
Yesterday we had error in logs: sysl
On Fri, Nov 17, 2017 at 3:39 AM, Amos Jeffries wrote:
> On 17/11/17 03:40, Bike dernikov1 wrote:
>>
>> Thanks for info, we searched for solution but found that is not
>> possible to combine delay polls, and forum is our last hope, so far we
>> solved almost everything :)
>> We have: Squid Object
I have already acted on it but couldn’t communicate in time, sorry. Thanks
for notifying and for looking into it.
On Fri, 17 Nov 2017 at 17:52, Amos Jeffries wrote:
> On 18/11/17 01:39, Walter H. wrote:
> > for more information see
> > https://www.ssllabs.com/ssltest/analyze.html?d=wiki.squid-c
On 18/11/17 01:45, Joe Foster wrote:
Good morning,
I have tried the attached but I still receive the same result.
I have attached a screen shot to show what happens, its like there is no
connection.
There isn't ...
I have tried it with and without listing 3128 as a safe ssl port. I
imagine
On 18/11/17 01:39, Walter H. wrote:
for more information see
https://www.ssllabs.com/ssltest/analyze.html?d=wiki.squid-cache.org
- missing intermediate certificate
- ssl3 active, poodle vulnerable ...
None of those issues appear in the test results I get from that URL you
referenced. SSLv3 i
On 18/11/17 04:27, Vieri wrote:
From: Alex Rousskov
1. Your "works" and "does not work" setups currently differ in at least
three variables: user agent name, slash after the user agent name, and
acl negation in http_access. Find out which single variable is
res
On 11/17/2017 08:27 AM, Vieri wrote:
> From: Alex Rousskov
>> 1. Your "works" and "does not work" setups currently differ in at least
>> three variables: user agent name, slash after the user agent name, and
>> acl negation in http_access. Find out which single variable is
>> responsible for the b
17.11.2017 21:27, Vieri пишет:
>
> From: Alex Rousskov
>> 1. Your "works" and "does not work" setups currently differ in at least
>> three variables: user agent name, slash after the user agent name, and
>> acl negation in http_access. Find out which single varia
From: Alex Rousskov
> 1. Your "works" and "does not work" setups currently differ in at least
> three variables: user agent name, slash after the user agent name, and
> acl negation in http_access. Find out which single variable is
> responsible for the breakage by
On 11/16/2017 08:39 PM, Amos Jeffries wrote:
> On 17/11/17 15:09, Richard Peeters wrote:
>> I have a requirement to forward proxy an opaque stream of data. One of
>> the servers (acting as a client -A- to SQUID ) will use the CONNECT
>> method to connect to SQUID (on server B) and squid will then p
Good morning,
I have tried the attached but I still receive the same result.
I have attached a screen shot to show what happens, its like there is no
connection.
I have tried it with and without listing 3128 as a safe ssl port. I
imagine its not needed as its generated from Squid.
HTTPS isn't
for more information see
https://www.ssllabs.com/ssltest/analyze.html?d=wiki.squid-cache.org
- missing intermediate certificate
- ssl3 active, poodle vulnerable ...
Greetings,
Walter
smime.p7s
Description: S/MIME Cryptographic Signature
___
squid-u
On 17/11/17 20:33, Bernhard Dübi wrote:
Hi,
I try to configure squid for a very special usecase but can't get it
to work. So, if you could give me some hints on how to do it right,
that would be great
Here's what I try to achieve:
the browser has proxy:8080 configured as manual proxy
from the
13 matches
Mail list logo
