Why does the content filter download or other proxy-initiated HTTPS requests fail?
Last Updated May 13, 2017
In some network environments, where SSLv2 handshakes are not permitted due to a low level of security inherent in such a request, it is prudent to change how the ProxySG appliance initiates these requests.
To fix this problem, change the SSL protocol version:
In the Management Console, navigate to Configuration > SSL > Device Profiles.
Select the default device profile and click Edit.
Change the SSL Protocol Version in the drop-down to support only SSLv3TLSv1.
Any sessions that were in progress at the time of the change will need time to clear before the change will impact a new session. Rebooting the appliance will ensure that this is done, otherwise wait between 5 and 15 minutes. This will ensure that any proxy-initiated HTTPS session (not user traffic) will use the updated value.
To control user traffic in a similar manner, make a similar change to the SSL client settings (in the Management Console, nagivate to Configuration >SSL > SSL Client).
Imported Document ID: 000016299
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
Subscribed to the Article.
Unable to subscribe
Thanks for your additional feedback !!!
Enterprise Support Virtual Agent
Rate Me :
Tell us more:
Welcome! My name is Sami, the Enterprise Support Virtual Agent answering technical support questions.