I can confirm that this configuration works as requested with the
configuration Jok Thuau had posted with the latest version 3.5.16.
Thank you so much for the response and the assistance.
On Thu, Apr 7, 2016 at 1:15 PM, Jok Thuau wrote:
> with 3.5.15, I have this config:
>
> ---8<---
> https_por
On 6/04/2016 3:27 a.m., Drikus Brits wrote:
>
>
> i believe i might have fixed it
>
> will advise soonest.
>
Any update?
Amos
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
On 5/04/2016 9:08 p.m., axel.eberha...@t-systems.com wrote:
> Hello,
>
> Maybe someone can give me a hint :-)
>
> I try to enable the Native ftp proxying.
> The documentation I have found is:
> http://wiki.squid-cache.org/Features/FtpRelay
>
> But there is no example for this. Also in the Mail A
On 8/04/2016 11:24 a.m., Luis Abdon Diaz Parra wrote:
> Hello, good day to ask quisera
> there any way atra instead of a domain allows me to upload all your files
> I mean a group of users only allow you to access a specific domain dstdomain
> say "facebook.com" but does not load your images that
On 8/04/2016 3:58 a.m., Markey, Bruce wrote:
> I'm running debian Jessie.
> Squid 3.5.16 compiled from source with the following:
>
>
> #allow/deny
> http_access allow internal
> http_access allow wireless
These...
> http_access deny !Safe_ports
> http_access deny CONNECT !SSL_ports
... secu
On 7/04/2016 1:34 p.m., crmanik wrote:
> Got this intersting log using -X option:
>
>
> *2016/04/06 18:34:53.817 kid1| Error negotiating SSL on FD 12:
> error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake
> failure (1/-1/0)
> *
Your OpenSSL library may not be supporting the
On 7/04/2016 5:24 a.m., Sebastien.Boulianne wrote:
> I configured my OWA to pass thru the Squid.
> Auth work perfectly.
> Browsing is working perfectly.
> All is working perfectly except when I try to attach files or documents to an
> email.
>
> [cid:image002.png@01D19007.A7E26D20]
>
>
> And It
On 9/04/2016 5:37 a.m., Yuri Voinov wrote:
>
> Don't think so. I've gave latest 4.0.8 tarball from site. Applied patch
> - viola! - issue is gone.
>
> 08.04.16 23:32, Odhiambo Washington пишет:
>> Hi Yuri,
>
>> I applied the patch against 4.0.8, not 3.5.16. Check my e-mail well
> well :-)
>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Don't think so. I've gave latest 4.0.8 tarball from site. Applied patch
- viola! - issue is gone.
08.04.16 23:32, Odhiambo Washington пишет:
> Hi Yuri,
>
> I applied the patch against 4.0.8, not 3.5.16. Check my e-mail well
well :-)
>
> Could it b
Hi Yuri,
I applied the patch against 4.0.8, not 3.5.16. Check my e-mail well well :-)
Could it be that you have a different code base from the tarballs available
for everyone?
On 8 April 2016 at 20:26, Yuri Voinov wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Note: Codebas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Note: Codebase for 4.0.x is different with 3.5.x. So, most patches for
4.x.x series can't be applied onto 3.5.x.
08.04.16 23:23, Odhiambo Washington пишет:
> Hi Yuri,
>
> Sorry to be a thorn in the flesh in this one.
>
> Which source code were yo
Hi Yuri,
Sorry to be a thorn in the flesh in this one.
Which source code were you applying this patch against?
I applied this patch on the released squid-4.0.8.tar.xz and it doesn't
apply cleanly for starters... Maybe I am doing it wrongly? Just doing patch
< /path/to/patch
wash@mail:~/ILI/Squi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I just put it here. :)
https://github.com/iangcarroll/ca-intermediaries
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBCAAGBQJXB9JKAAoJENNXIZxhPexGyJwIAIYFfDZwBQ3CZJIDyWpNKvi1
URyu5/+JXTYf6CMR2ZSuuNaLSkLOjPAlI4itsbSX8hM/j4UBISJ5lQDTV7KH
On 8 April 2016 at 17:59, Amos Jeffries wrote:
> On 9/04/2016 2:38 a.m., Odhiambo Washington wrote:
> > Now that Yuri has reported success, shall I wait for something for
> 3.5.16??
>
> No that means his problem was unrelated to yours.
>
Alright.
>
> The 3.5.16 code in this area was correctly
On 9/04/2016 2:38 a.m., Odhiambo Washington wrote:
> Now that Yuri has reported success, shall I wait for something for 3.5.16??
No that means his problem was unrelated to yours.
The 3.5.16 code in this area was correctly using errno. So the message
it was giving you was correct for your issue.
Now that Yuri has reported success, shall I wait for something for 3.5.16??
Could it be that I am the onlt one trying 3.5.16 on this old version of
FreeBSD? I am saying that because it is running well on FreeBSD-10.3 since
two days ago.
There is another e-mail I sent about 4.0.8 failing to compile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Seems fixed.
http://bugs.squid-cache.org/show_bug.cgi?id=4486#c2
08.04.16 18:05, Amos Jeffries пишет:
> On 8/04/2016 10:28 p.m., Odhiambo Washington wrote:
>> Hello Yuri,
>>
>> Thanks, but this patch is for squid-4.0.8, right??
>>
>
> Yes the pat
On 8/04/2016 10:28 p.m., Odhiambo Washington wrote:
> Hello Yuri,
>
> Thanks, but this patch is for squid-4.0.8, right??
>
Yes the patch in that bug report is specific to the latest 4.0 snapshot,
which Yuri is running.
As Alex mentioned the errno usage in Squid was a bit wrong. The latest
4.0 h
Hello Yuri,
Thanks, but this patch is for squid-4.0.8, right??
If applied to 3.5.16, the compilation fails as follows:
depbase=`echo mem/Segment.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;
/bin/bash ../../libtool --tag=CXX--mode=compile g++ -DHAVE_CONFIG_H
-DDEFAULT_STATEDIR=\"/opt/squid-3.5
19 matches
Mail list logo
