Aw: Re: [users@httpd] Set SSLCipherSuite dependent on client IP

2021-02-24 Thread Hildegard Meier
Thank you very much Eric, for your quick response and explanation. Do you have a source for it (aside of the source code ;) ? I thought about something like that as cause, but since the client IP is known from the very first start of the request, before TLS handshake, I thought it could be eval

Re: [users@httpd] Set SSLCipherSuite dependent on client IP

2021-02-24 Thread Eric Covener
> Why does this not work? is evaluated early in request processing, long after the handshake. However, the manual says: In per-directory context it forces a SSL renegotiation with the reconfigured Cipher Suite after the HTTP request was read but before the HTTP response is sent. I suggest testin

Aw: [users@httpd] Set SSLCipherSuite dependent on client IP

2021-02-24 Thread Hildegard Meier
P.S. Nevermind the port 4433 in the example, that's because load balancer port natting. The vHost works fine with outbound port 443. This question is only about the if/else block in combination with SSLCipherSuite. > Gesendet: Mittwoch, 24. Februar 2021 um 14:12 Uhr > Von: "Hildegard Meier" >

[users@httpd] Set SSLCipherSuite dependent on client IP

2021-02-24 Thread Hildegard Meier
Hello, having Ubuntu 14 server with Apache 2.4.7 I configured to have SSLCipherSuite dependent on the client IP address. But the If/Else directive seems to be just silently ignored, only and always the global default SSLCipherSuite value is in effect. The SSLCipherSuite given in the If or Else