I tried to install a joomla-Plugin from behind squid. It didn't work. I could
reproduce the error using the following php-script:
> $url="https://downloads.joomla.org/extensions/install-from-web/1-1-1/
plg_webinstaller_3.7v1.1.1.zip";
> $ctx = stream_context_create(['http' => ['proxy' => "tcp:/
Am Samstag, 17. Februar 2018, 14:28:04 CET schrieb chiasa.men:
> Am Montag, 12. Februar 2018, 14:29:09 CET schrieb chiasa.men:
> > Hi I tried squid4.
> >
> > Squid Cache: Version 4.0.23
> > This binary uses OpenSSL 1.1.1-dev xx XXX
> >
> > Before,
Am Montag, 12. Februar 2018, 14:29:09 CET schrieb chiasa.men:
> Hi I tried squid4.
>
> Squid Cache: Version 4.0.23
> This binary uses OpenSSL 1.1.1-dev xx XXX
>
> Before, I used:
> Squid Cache: Version 3.5.27
> This binary uses OpenSSL 1.0.2g 1 Mar 2016
>
>
Hi I tried squid4.
Squid Cache: Version 4.0.23
This binary uses OpenSSL 1.1.1-dev xx XXX
Before, I used:
Squid Cache: Version 3.5.27
This binary uses OpenSSL 1.0.2g 1 Mar 2016
Some of the config directives changed:
E.g.
sslproxy_options SINGLE_DH_USE,SINGLE_ECDH_USE
->
tls_tls_outgoing_
I have to restart squid after each reboot to get it working. I think that is
because squid starts before systemd has started the network and so the dns
lookups fail:
journalctl says:
"squid.service: Unit cannot be reloaded because it is inactive."
cache.log contains:
"WARNING: DNS lookup for 'e
Am Dienstag, 5. September 2017, 11:57:06 CEST schrieb Amos Jeffries:
> On 05/09/17 20:55, chiasa.men wrote> Thanks, that was easy... but:
> > That does not work:
> >
> > https_port 3128 accel defaultsite=www.example.com cert=/example/cert.pem
> > key=/ example/key
Am Montag, 4. September 2017, 14:07:54 CEST schrieb Amos Jeffries:
> On 04/09/17 20:36, chiasa.men wrote:
> > "RC4-MD5" seems to be always enabled. Is there a way to prohibit RC4-MD5?
> >
> >
> >
> > squid.conf:
> > https_port 3128 accel d
"RC4-MD5" seems to be always enabled. Is there a way to prohibit RC4-MD5?
squid.conf:
https_port 3128 accel defaultsite=www.example.com cert=/example/cert.pem key=/
example/key.pem
sslproxy_version 6
sslproxy_options NO_SSLv2,NO_SSLv3,NO_TLSv1,NO_TLSv1_1,NO_TICKET
sslproxy_cipher ECDHE-ECDSA-AES
Am Freitag, 12. Mai 2017, 14:16:45 CEST schrieb Amos Jeffries:
> On 12/05/17 22:31, chiasa.men wrote:
> > Am Sonntag, 23. April 2017, 17:57:52 CEST schrieb Amos Jeffries:
> >> On 23/04/17 23:25, chiasa@web.de wrote:
> >>> Hello
> >>
Am Sonntag, 23. April 2017, 17:57:52 CEST schrieb Amos Jeffries:
> On 23/04/17 23:25, chiasa@web.de wrote:
> > Hello
> >
> > my squid.conf looks like that:
> >
> > https_port 3128 accel cert=/cert.pem key=/cert.key
> >
> > defaultsite=ww1.example.com vhost
> >
> > acl server20_domains dstdo
Am Sonntag, 23. April 2017, 18:03:25 CEST schrieb Amos Jeffries:
> You appear not to be using curl correctly.
>
> Test #1 and #3 show that curl is probably sending the https:// requests
> through port 8080 on your proxy as a CONNECT request. Check that in your
> Squid log to confirm.
I wasn't aw
Hello folks
I tried to encrypt the connection between client and squid. Therefore I
generated certificates which are accepted by the clients and configured squid
as followed:
Squid.conf
https_port 10.0.13.10:8443 cert=/cert.pem key=/cert.key
http_port 10.0.13.10:8080
http_access allow all
hello
there a two cache_peers with ssl enabled webservers. Obviously for both the
private keys are available.
For http_port squid can use header_access to filter headers.
Can squid make use of the known private keys in order to filter the headers for
https_port connetions too?
How?
Is the any me
13 matches
Mail list logo
