#
#
#
#
#
#
#
o ssl-accurate-shutdown:
This forces an accurate shutdown when the connection is closed,
i.e. a
SSL close notify alert is sent and mod_ssl waits for the close
notify
alert of the client. This is 100% SSL/TLS standard compliant,
but in
practice often causes hanging connections with brain-dead
browsers. Use
this only for browsers where you know that their SSL
implementation
works correctly.
# Notice: Most problems of broken clients are also related to the
HTTP
# keep-alive facility, so you usually additionally want to disable
# keep-alive for those clients, too. Use variable "nokeepalive" for
this.
# Similarly, one has to force some clients to use HTTP/1.0 to
workaround
# their broken HTTP/1.1 implementation. Use variables
"downgrade-1.0" and
# "force-response-1.0" for this.
BrowserMatch "MSIE [2-5]" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
# Per-server logging:
# The home of a custom SSL log file. Use this when you want a
# compact non-error SSL log file on a virtual host basis.
CustomLog "/usr/local/apache2/logs/ssl_request_log" \
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
</VirtualHost>
Installation/configuration
4.5 SIMATIC IoT2040
Manage MyMachines /Remote - installation in existing control environments
74 Application examples, 10/2018, A5E45211403B AB
To Next Page
Loading...
