HP StorageWorks Command View XP Advanced Edition Device Manager Server Installation and Configuration Guide (December 2005)

Command View XP AE Device Manager Server Properties 118
7-2-11 server.http.socket.linger
This Boolean property toggles whether the SO_LINGER socket attribute is enabled for client
connections with the Device Manager server. Setting this flag to its default value means a linger-on-
close timeout of 60 seconds is applied to socket connections. You should only modify this property if
you are an expert System Administrator seeking to fine-tune the server’s performance.
Default: true
7-2-12 server.http.socket.noDelay
This Boolean property toggles whether the TCP_NODELAY socket attribute is enabled for
connections to the Device Manager server. Setting this flag at its default value disables the Nagle
algorithm for TCP/IP packets. You should only modify this property if you are an expert System
Administrator seeking to fine-tune the server’s performance.
Default: true
7-2-13 server.http.headers.maxNumber
This property sets the maximum number of HTTP headers permitted for any request submitted to the
Device Manager web server, and helps prevent certain types of denial of service and attempted buffer
overflow attacks by restricting the effect of malicious requests containing a large number of headers.
You should not need to change this setting under normal circumstances. The Device Manager server
silently ignores any HTTP headers in excess of this number. Runtime errors are not automatically
generated under such circumstances.
Default: 20
7-2-14 server.http.headers.maxLength
This property sets the maximum length permitted for any HTTP header (in bytes). You should not
need to change this setting under normal circumstances. It helps prevent certain types of denial of
service and attempted buffer-overflow attacks by restricting the effect of malicious requests that
contain unusually large header fields. Headers longer than the specified length will be truncated by
the Device Manager server without automatically generating runtime errors.
Default: 1024
7-2-15 server.http.entity.maxLength
This property sets the maximum length of an HTTP request entity (in bytes). You should not need to
change this setting under normal circumstances. It helps prevent certain types of denial of service and
attempted buffer overflow attacks by restricting the effect of malicious requests that contain unusually
large payload entities. If the server detects a posted request longer than this value, it sends an error
response to the client and logs details of the attempted request.
Default: 131072
7-2-16 server.http.log.reverseDNS
This Boolean property flags whether the Device Manager server performs reverse-DNS (Domain
Name Server) lookup for its access logging. When set, this property the server attempts to resolve the
name of a client from the IP address for incoming connections. If the client’s IP address can be
resolved, the domain name is also written into the server’s access log. Not all IP addresses on the
Internet have an assigned domain name, so some logged requests might still be recorded as a
numeric IP address, even with this flag turned on.
NOTE: While translation of the IP address to a domain name can assist analysis of the server’s access logs,
reverse-DNS lookups are expensive in terms of resources, and this feature may significantly degrade the
server’s performance, especially on a slow network. You should keep the setting at the default value for
better performance.