On 04/20/2017 11:34 PM, Amos Jeffries wrote:
> On 21/04/17 15:37, 钱国正 wrote:
>> I know squid+ecap can modify http response with a relatively fast
>> speed, and I have done that before.
>> But, in real environment, there is a lot of reqeusts, that don't need
>> processs http response, which would ma
I see no problem with it on all five SSL Bump-aware servers with new
Chrome. So fare so good.
21.04.2017 18:29, Marko Cupać пишет:
> Hi,
>
> I have squid setup with ssl bump which worked fine, but since I updated
> chrome to 58 it won't display any https sites, throwing
> NTT:ERR_CERT_COMMON_NAME
Hi,
I have squid setup with ssl bump which worked fine, but since I updated
chrome to 58 it won't display any https sites, throwing
NTT:ERR_CERT_COMMON_NAME_INVALID. https sites still work in previous
chrome version, as well as in IE.
Anything I can do in squid config to get ssl-bumped sites in c