Cisco Cisco IOS Software Release 12.2(27)SBC

Descargar
Página de 68
HTTP 1.1 Web Server and Client
  Restrictions for HTTP 1.1 Web Server and Client
2
Cisco IOS Network Management Configuration Guide
Restrictions for 
HTTP 1.1 Web Server and Client
The secure HTTP (HTTPS) server and client—secure HTTP communication in which Secure Socket 
Layer (SSL) encryption technology provides HTTP server and client authentication and is used to 
encrypt data sent to and received from an HTTP server—are not supported in the HTTP 1.1 web server 
and client feature in Cisco IOS Release 12.2(31)SB2. 
Information About the 
HTTP 1.1 Web Server and Client
To use the HTTP 1.1 web server and client, you should understand the following concepts:
HTTP 1.1 with Cisco Devices
This feature updates the Cisco implementation of HTTP from 1.0 to 1.1. The HTTP server allows 
features and applications, such as the Cisco web browser user interface, to be run on your routing device.
The Cisco implementation of HTTP 1.1 is backward compatible with previous Cisco IOS releases. If you 
are currently using configurations that enable the HTTP server, no configuration changes are needed, as 
all defaults remain the same.
The process of enabling and configuring the HTTP server also remains the same as in previous releases. 
Support for Server Side Includes (SSI) and HTML forms has not changed. Additional configuration 
options, in the form of the ip http timeout-policy command and the ip http max-connections command 
have been added. These options allow configurable resource limits for the HTTP server. If you do not 
use these optional commands, the default policies are used.
Remote applications may require that you enable the HTTP server before using them. Applications that 
use the HTTP server include the following:
Cisco web browser user interface—This user interface uses the Cisco IOS Homepage Server, 
HTTP-based EXEC Server, and HTTP IOS File System (IFS) Server.
VPN Device Manager (VDM) application—VDM uses the VDM Server and the XML Session 
Manager (XSM).
QoS Device Manager (QDM) application—QDM uses the QDM Server. 
HTTP Server General Access Policies
General access characteristics for the server can be specified using the ip http timeout-policy command 
to configure a value for idle time, connection life, and request maximum. By adjusting these values you 
can configure a general policy; for example, if you want to maximize throughput for HTTP connections, 
you should configure a policy that minimizes connection overhead. You can configure such a policy by 
specifying large values for the life and request options so that each connection stays open longer and 
more requests are processed for each connection.