![]() |
Cisco IOS HTTP Services Command Reference
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
clear ip http client cookie through show ip http server secure status
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contents
clear ip http client cookie through show ip http server secure status clear ip http client cookieTo remove the HTTP client cookies, use the clear ip http client cookie command in privileged EXEC mode. Syntax Description
ip http access-classTo specify the access list that should be used to restrict access to the HTTP server, use the ip http access-class command in global configuration mode. To remove a previously configured access list association, use the no form of this command. Command History
Usage GuidelinesIf this command is configured, the specified access list is assigned to the HTTP server. Before the HTTP server accepts a connection, it checks the access list. If the check fails, the HTTP server does not accept the request for a connection. ExamplesThe following example shows how to define an access list as 20 and assign it to the HTTP server: Router(config)# ip access-list standard 20 Router(config-std-nacl)# permit 209.165.202.130 0.0.0.255 Router(config-std-nacl)# permit 209.165.201.1 0.0.255.255 Router(config-std-nacl)# permit 209.165.200.225 0.255.255.255 ! (Note: all other access implicitly denied) Router(config-std-nacl)# exit Router(config)# ip http access-class 20 ip http accounting commandsTo specify a command accounting method for HTTP server users, use the ip http accounting commands command in global configuration mode. To disable a configured command accounting method, use the no form of this command.
ip
http
accounting
commands
level
{default | named-accounting-method-list}
no
ip
http
accounting
commands
level
Syntax DescriptionCommand DefaultCommand accounting for HTTP and HTTP over Secure Socket Layer (HTTPS) is automatically enabled when authentication, authorization, and accounting (AAA) is configured on the device. It is not possible to disable accounting for HTTP and HTTPS. HTTP and HTTPS will default to using the global AAA default method list for accounting. The ip http accounting commands can be used to configure HTTP and HTTPS to use any predefined AAA method list. Usage GuidelinesCommand accounting provides information about the commands, executed on a device, for a specified privilege level. Each command accounting record corresponds to one IOS command executed at its respective privilege level, the date and time the command was executed, and the user who executed it. Command accounting will be implemented for HTTP and HTTPS. A stop accounting record will be generated for any command execution/configuration done by a user via HTTP and HTTPS. If this command is not configured, HTTP and HTTPS will use the default AAA accounting list whenever AAA is enabled using the aaa new-model configuration command. If the default method list does not exist, no accounting records will be generated. Whenever AAA is disabled, no accounting records will be generated.
ExamplesThe following example shows how to configure HTTP and HTTPS to allow AAA accounting support: Router(config)# ip http accounting commands 1 oneacct
Related Commands
ip http active-session-modulesTo selectively enable HTTP applications that will service incoming HTTP requests from remote clients, use the ip http active-session-modules command in global configuration mode. Use the no form of this command to return to the default, for which all HTTP services will be enabled. Syntax Description
Usage GuidelinesUse the ip http active-session-modules command to selectively enable HTTP applications, for servicing incoming HTTP requests from remote clients. With this command, a selected list of applications can be enabled. All the applications can be enabled or none of the applications can be enabled, in other words, all disabled. Use the ip http session-module-list command to define a list of HTTP or secure HTTP (HTTPS) application names to be enabled. If an HTTP request is made for a service that is disabled, a 404 error message is displayed in the remote client browser.
ExamplesThe following example shows how to configure a different set of services to be available for HTTP and HTTPS requests. In this example, all HTTP applications are enabled for providing services to remote clients, but for HTTPS services, only the HTTPS applications defined in list1 (Simple Certificate Enrollment Protocol [SCEP] and HOME_PAGE) are enabled. ip http session-module-list list1 SCEP,HOME_PAGE ip http active-session-modules all ip http server ip http secure-server ip http secure-active-session-modules list1 Related Commands
ip http authenticationTo specify a particular authentication method for HTTP server users, use the ip http authentication command in global configuration mode. To disable a configured authentication method, use the no form of this command.
ip
http
authentication
{aaa {command-authorization level listname | exec-authorization listname | login-authentication listname} | enable | local | tacacs}
no
ip
http
authentication
{aaa {command-authorization level listname | exec-authorization listname | login-authentication listname} | enable | local | tacacs}
Syntax DescriptionCommand DefaultThe âenableâ password is required when users (clients) connect to the HTTP server. Three command privilege levels exist on the router. Command History
Usage GuidelinesThe ip http authentication command specifies the authentication method to be used for login when a client connects to the HTTP server. Use of the aaa option is recommended. The enable, local, and tacacs methods should be specified using the aaa authentication login command. The âenableâ password method is the default HTTP server authentication method. If the enable password is used as the HTTP server login authentication method, the client connects to the HTTP server with a default privilege level of 15. ExamplesThe following example shows how to specify that AAA should be used for authentication for HTTP server users. The AAA login method is configured as the âlocalâ username/password authentication method. This example also shows how to specify using the local username database for login authentication and EXEC authorization of HTTP sessions: Router(config)# aaa authentication login LOCALDB local Router(config)# aaa authorization exec LOCALDB local Router(config)# ip http authentication aaa login-authentication LOCALDB Router(config)# ip http authentication aaa exec-authorization LOCALDB ip http client cacheTo configure the HTTP client cache, use the ip http client cache command in global configuration mode. To remove the specification of a value configured for the HTTP client cache, use the no form of this command.
ip http client cache
{ager interval minutes | memory {memory file-size-limit | pool pool-size-limit}}
no
ip
http
client
cache
{ager interval | memory {file | pool}}
Syntax DescriptionCommand Default5 second ager interval for the HTTP client cache memory pool 2 KB maximum file size supported by the HTTP client cache 100 KB maximum memory pool size for the HTTP client cache Usage GuidelinesUse this command to specify the HTTP client cache ager interval, maximum file size, or maximum memory pool size. To display the values configured by this command, use the show ip http client cache command. ExamplesThe following example shows how to specify an HTTP client cache ager interval of 10 minutes:
Router(config)# ip http client cache ager interval 10
The following example shows how to specify an HTTP client cache maximum file size of 7 KB:
Router(config)# ip http client cache memory file 7
The following example shows how to specify an HTTP client cache maximum memory pool size of 55 KB:
Router(config)# ip http client cache memory pool 55
Related Commands
ip http client connectionTo configure an HTTP client connection to a remote HTTP server for file transfers, use the ip http client connectioncommand in global configuration mode. To remove the configuration, use the no form of this command.
ip
http
client
connection
{forceclose | idle timeout seconds | pipeline-length length | retry count | timeout seconds}
no
ip
http
client
connection
{forceclose | idle | pipeline-length | retry | timeout}
Syntax Description
Command History
ExamplesThe following example shows how to configure an idle connection time of 15 seconds for an HTTP client persistent connection.
Router(config)# ip http client connection idle timeout 15
Related Commands
ip http client passwordTo configure the default password used for connections to remote HTTP servers, use the ip http client password command in global configuration mode. To remove a configured default password from the configuration, use the no form of this command. Command History
Usage GuidelinesThis command is used to configure a default password before a file is downloaded from a remote web server using the copy http:// or copy https:// command. The default password will be overridden by a password specified in the URL of the copycommand. The password is encrypted in the configuration files.
ExamplesIn the following example, the default HTTP password is configured as Password and the default HTTP username is configured as User2 for connections to remote HTTP or HTTPS servers: Router(config)# ip http client password Password Router(config)# ip http client username User2 Router(config)# do show running-config | include ip http client Related Commands
ip http client proxy-serverTo configure an HTTP proxy server, use the ip http client proxy-server command in global configuration mode. To disable or change the proxy server, use the no form of this command. Usage GuidelinesThis command configures the HTTP client to connect to a remote proxy server for HTTP file system client connections. ExamplesThe following example shows how to configure the HTTP proxy server named edge2 at port 29:
Router(config)# ip http client proxy-server edge2 proxy-port 29
Related Commands
ip http client responseTo configure the number of seconds that the HTTP client waits for a response from the server for a request message, use the ip http client response command in global configuration mode. To remove the specified number of seconds that the HTTP client waits for a response, use the no form of this command. ExamplesThe following example shows how to specify a response timeout of 180 seconds:
Router(config)# ip http client response timeout 180
Related Commands
ip http client secure-ciphersuiteTo specify the CipherSuite that should be used for encryption over the secure HTTP connection from the client to a remote server, use the ip http client secure-ciphersuite command in global configuration mode. To remove a previously configured CipherSuite specification for the client, use the no form of this command.
ip
http
client
secure-ciphersuite
[3des-ede-cbc-sha]
[rc4-128-sha]
[rc4-128-md5]
[des-cbc-sha]
no
ip
http
client
secure-ciphersuite
Syntax Description
Command DefaultThe client and server negotiate the best CipherSuite that they both support from the list of available CipherSuites. Usage GuidelinesThis command allows you to restrict the list of CipherSuites (encryption algorithms) that the client offers when connecting to a secure HTTP server. For example, you may want to allow only the most secure CipherSuites to be used. Unless you have a reason to specify the CipherSuites that should be used, or you are unfamiliar with the details of these CipherSuites, you should leave this command unconfigured and let the server and client negotiate the CipherSuite that they both support (this is the default). The no form of this command returns the list of available CipherSuites to the default (that is, all CipherSuites supported on your device are available for negotiation). ip http client secure-trustpointTo specify the remote certificate authority (CA) trustpoint that should be used if certification is needed for the secure HTTP client, use the ip http client secure-trustpoint command in global configuration mode. To remove a client trustpoint from the configuration, use the no form of this command.
ip
http
client
secure-trustpoint
trustpoint-name
no
ip
http
client
secure-trustpoint
trustpoint-name
Command DefaultIf the remote HTTPS server requests client certification, the secure HTTP client will use the trustpoint configured using the primary command in the CA trustpoint configuration. If a trustpoint is not configured, client certification will fail. Usage GuidelinesThis command specifies that the secure HTTP client should use the certificate associated with the trustpoint indicated by the trustpoint-name argument. Use the same trustpoint name that you used in the associated crypto ca trustpoint command. The specified X.509v3 security certificate will be used by the HTTPS client for cases when the remote HTTPS server requires client authorization. Use this command only if you have already declared a CA trustpoint using the crypto ca trustpoint command and associated submode commands. If the remote HTTPS server requires client authorization and a trustpoint is not configured for the client, the remote HTTPS server will reject the connection. If this command is not used, the client attempts to use the certificate associated with the primary trustpoint. The primary trustpoint is configured using the primary command. ExamplesIn the following example, the CA trustpoint is configured and referenced in the secure HTTP server configuration: !The following commands specify a CA trustpoint that can be used !to obtain a X.509v3 security certificate. Router(config)# crypto ca trustpoint tp1 Router(config-ca)# enrollment url http://host1:80 Router(config-ca)# exit !The following command is used to actually obtain the security certificate. !A trustpoint NAME is used because there could be multiple trust points !configured for the router. Router(config)# crypto ca enrollment TP1 !The following command specifies that the secure HTTP client !should use the certificate associated with the TP1 trustpoint for HTTPS connections. Router(config)# ip http client secure-trustpoint tp1 ip http client source-interfaceTo configure a source interface for the HTTP client, use the ip http client source-interface command in global configuration mode. To change or disable the source interface, use the no form of this command. ExamplesThe following example shows how to configure the source interface as Ethernet 0/1:
Router(config)# ip http client source-interface Ethernet 0/1
Related Commands
ip http client usernameTo configure the default username used for connections to remote HTTP servers, use the ip http client username command in global configuration mode. To remove a configured default HTTP username from the configuration, use the no form of this command. Usage GuidelinesThis command is used to configure a default username before a file is copied to or from a remote web server using the copy http:// or copy https:// command. The default username will be overridden by a username specified in the URL of the copycommand.
ExamplesIn the following example, the default HTTP password is configured as Secret and the default HTTP username is configured as User1 for connections to remote HTTP or HTTPS servers: Router(config)# ip http client password Secret Router(config)# ip http client username User1 Related Commands
ip http digest algorithmip http help-pathTo configure the help root used to locate help files for use by the userâs current GUI screen, use the ip http help-path command in global configuration mode. Usage GuidelinesThe URL specified in this command must be populated with âhelpâ files with read access that are appropriate for the application that will be using the URL. ip http max-connectionsTo configure the maximum number of concurrent connections allowed for the HTTP server, use the ip http max-connections command in global configuration mode. To return the maximum connection value to the default, use the no form of this command. Usage GuidelinesPlatform-specific implementations can supersede the upper range limit of 16. If a new value is configured that is less than the previously configured value while the current number of connections exceeds the new maximum value, the HTTP server will not abort any of the current connections. However, the server will not accept new connections until the current number of connections falls below the new configured value. ip http pathTo specify the base path used to locate files for use by the HTTP server, use the ip http path command in global configuration mode. To remove the base path specification, use the no form of this command. Command History
Usage GuidelinesAfter enabling the HTTP server, you should set the base path by specifying the location of the HTML files to be served. HTML files used by the HTTP web server typically reside in system flash memory. Remote URLs can be specified using this command, but use of remote path names (for example, where HTML files are located on a remote TFTP server) is not recommended. ExamplesIn the following example, the HTML files are located in the default flash location on the system:
Router(config)# ip http path flash:
In the following example, the HTML files are located in the directory named web on the flash memory card inserted in slot 0:
Router(config)# ip http path slot0:web
ip http portTo specify the port number to be used by the HTTP server, use the ip http portcommand in global configuration mode. To return the port number to the default, use the no form of this command. Command History
Usage GuidelinesHTTP port 80 is the standard port used by web servers.
ip http secure-active-session-modulesTo selectively activate HTTP Secure (HTTPS) services to process incoming HTTPS requests from remote clients, use the ip http secure-active-session-modules command in global configuration mode. To return to the default in which all HTTPS services are activated, use the no form of this command.
ip
http
secure-active-session-modules
{listname | all | none}
no
ip
http
secure-active-session-modules
Usage GuidelinesUse the ip http secure-active-session-modules command to activate or deactivate HTTPS services to process incoming HTTPS requests from remote clients. Use the ip http session-module-list command to define a list of HTTP or HTTPS services to be enabled. If an HTTPS request is made for a service that is disabled, an error message is displayed in the remote client browser. ExamplesThe following example shows how to configure different sets of services to be available for HTTP and HTTPS requests. In this example, all HTTP services are activated, but only the HTTPS services defined in list1 (Simple Certificate Enrollment Protocol [SCEP] and HOME_PAGE) are activated. ip http session-module-list list1 SCEP,HOME_PAGE ip http active-session-modules all ip http server ip http secure-server ip http secure-active-session-modules list1 ip http secure-ciphersuiteTo specify the CipherSuites that should be used by the secure HTTP server when negotiating a connection with a remote client, use the ip http secure-ciphersuite command in global configuration mode. To return the configuration to the default set of CipherSuites, use the no form of this command.
ip
http
secure-ciphersuite
[3des-ede-cbc-sha]
[rc4-128-sha]
[rc4-128-md5]
[des-cbc-sha]
no
ip
http
secure-ciphersuite
Syntax Description
Command DefaultThe HTTPS server negotiates the best CipherSuite using the list received from the connecting client. Usage GuidelinesThis command is used to restrict the list of CipherSuites (encryption algorithms) that should be used for encryption over the HTTPS connection. For example, you may want to allow only the most secure CipherSuites to be used. Unless you have a reason to specify the CipherSuites that should be used, or you are unfamiliar with the details of these CipherSuites, you should leave this command unconfigured and let the server and client negotiate the CipherSuite that they both support (this is the default). The supported CipherSuites vary by Cisco IOS software image. For example, âIP Sec56â (âk8â) images support only the SSL_RSA_WITH_DES_CBC_SHA CipherSuite in Cisco IOS Release 12.2(15)T. In terms of router processing load (speed), the following list ranks the CipherSuites from fastest to slowest (slightly more processing time is required for the more secure and more complex CipherSuites):
Additional information about these CipherSuites can be found online from sources that document the Secure Sockets Layer (SSL) 3.0 protocol. ip http secure-client-authTo configure the secure HTTP server to authenticate connecting clients, use the ip http secure-client-auth command in global configuration mode. To remove the requirement for client authorization, use the no form of this command. Usage GuidelinesThis command configures the HTTP server to request an X.509v3 certificate from the client in order to authenticate the client during the connection process. In the default connection and authentication process, the client requests a certificate from the HTTP server, but the server does not attempt to authenticate the client. Authenticating the client provides more security than server authentication by itself, but not all web clients may be configured for certificate authority (CA) authentication. ip http secure-portTo set the secure HTTP (HTTPS) server port number for listening, use the ip http secure-port command in global configuration mode. To return the HTTPS server port number to the default, use the no form of this command. Command History
Usage GuidelinesAn HTTP server and an HTTPS server cannot use the same port. If you try to configure both on the same port, the following message is displayed: % Port port_number in use by HTTP. where port_number is the port number that is already assigned to the HTTP server. If you change the HTTPS port number, clients attempting to connect to the HTTPS server must specify the port number in the URL, in this format: https://device:port_number where port_number is the HTTPS port number. ip http secure-serverTo enable a secure HTTP (HTTPS) server, use the ip http secure-server command in global configuration mode. To disable an HTTPS server, use the no form of this command. Command History
Usage GuidelinesThe HTTPS server uses the Secure Sockets Layer (SSL) version 3.0 protocol.
If a certificate authority (CA) is used for certification, you should declare the CA trustpoint on the routing device before enabling the HTTPS server. ExamplesIn the following example the HTTPS server is enabled, and the (previously configured) CA trustpoint CA-trust-local is specified: Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip http secure-server Router(config)# ip http secure-trustpoint CA-trust-local Router(config)# end Router# show ip http server secure status HTTP secure server status: Enabled HTTP secure server port: 443 HTTP secure server ciphersuite: 3des-ede-cbc-sha des-cbc-sha rc4-128-md5 rc4-12a HTTP secure server client authentication: Disabled HTTP secure server trustpoint: CA-trust-local Related Commands
ip http secure-trustpointTo specify the certificate authority (CA) trustpoint that should be used for obtaining signed certificates for a secure HTTP (HTTPS) server, use the ip http secure-trustpoint command in global configuration mode. To remove a previously specified CA trustpoint, use the no form of this command. Command DefaultThe HTTPS server uses the trustpoint configured when you use the primary command. If a trustpoint is not configured, the HTTPS server uses a self-signed certificate. Usage GuidelinesThis command specifies that the HTTPS server should use the X.509v3 certificate associated with the trustpoint indicated by the trustpoint-name argument. Use the same trustpoint name that you used in the associated crypto ca trustpointcommand. The specified X.509v3 security certificate will be used to authenticate the server to connecting clients, and, if remote client authentication is enabled, to authenticate the connecting clients. Use this command only if you have already declared a CA trustpoint using the crypto ca trustpoint command and associated submode commands. If a trustpoint is not configured, the HTTPS server will use a self-signed certificate. If this command is not used, the server will attempt to use the certificate associated with the primary trustpoint. The primary trustpoint is configured using the primary command. ExamplesIn the following example, the CA trustpoint is configured, a certificate is obtained, and the certificate is referenced in the HTTPS server configuration: !The following commands specifies a CA trustpoint that can be used !to obtain a X.509v3 security certificate. !A trustpoint NAME is used because there could be multiple trustpoints !configured for the router. Router(config)# crypto ca trustpoint tp1 Router(config-ca)# enrollment url http://host1:80 Router(config-ca)# exit Router(config)# crypto ca authenticate tp1 !The following command is used to actually obtain the security certificate. Router(config)# crypto ca enrollment tp1 Router(config)# ip http secure-server !The following command specifies that the secure HTTP server !should use a certificate associated with the TP1 trustpoint for HTTPS connections. Router(config)# ip http secure-trustpoint tp1 Related Commands
ip http serverTo enable the HTTP server on your IP or IPv6 system, including the Cisco web browser user interface, use the ip http servercommand in global configuration mode. To disable the HTTP server, use the no form of this command. Command DefaultThe HTTP server is disabled on the Cisco Catalyst 4000 series switch. The HTTP server is enabled for clustering on the following Cisco switches: Catalyst 3700 series, Catalyst 3750 series, Catalyst 3550 series, Catalyst 3560 series, and Catalyst 2950 series. The HTTP server uses the standard port 80 by default. Command History
Usage GuidelinesWith IPv6 support added in Cisco IOS Release 12.2(2)T, the ip http server command simultaneously enables and disables both IP and IPv6 access to the HTTP server. However, an access list configured with the ip http access-class command will only be applied to IPv4 traffic. IPv6 traffic filtering is not supported.
ip http session-module-listTo define a list of HTTP or secure HTTP (HTTPS) application names, use the ip http session-module-list command in global configuration mode. To remove the defined list, use the no form of this command.
ip http session-module-list
listname
prefix1
[prefix2,...,prefixn]
no ip http session-module-list
listname
prefix1
[prefix2,...,prefixn]
Syntax Description
Usage GuidelinesUse this command to define a list of HTTP or HTTPS application names. The defined list can then be used by the ip http active-session-modules or ip http secure-active-session-modulescommands to selectively enable HTTP or HTTPS applications, respectively, for servicing incoming HTTP and HTTPS requests from remote clients. When defining a list of HTTP or HTTPS application names, use the following guidelines:
ExamplesThe following example shows how to configure a different set of services to be available for HTTP and HTTPS requests. In this example, all HTTP applications are enabled for providing services to remote clients, but for HTTPS services, only the HTTPS applications defined in list1 (Simple Certificate Enrollment Protocol [SCEP] and HOME_PAGE) are enabled. ip http session-module-list list1 SCEP,HOME_PAGE ip http active-session-modules all ip http server ip http secure-server ip http secure-active-session-modules list1 Related Commands
ip http timeout-policyTo configure the parameters for closing connections to the local HTTP server, use the ip http timeout-policy command in global configuration mode. To return the parameters to their defaults, use the no form of this command. Syntax Description
Command DefaultHTTP server connection idle time: 180 seconds (3 minutes) HTTP server connection life time: 180 seconds (3 minutes) HTTP server connection maximum requests: 1 Usage GuidelinesThis command sets the characteristics that determine how long a connection to the HTTP server should remain open. This command may not take effect immediately on any HTTP connections that are open at the time you use this command. In other words, new values for idle time, life time, and maximum requests will apply only to connections made to the HTTP server after this command is issued. A connection may be closed sooner than the configured idle time if the server is too busy or the limit on the life time or the number of requests is reached. Also, since the server will not close a connection while actively processing a request, the connection may remain open longer than the specified life time if processing is occurring when the life maximum is reached. In this case, the connection will be closed when processing finishes. A connection may be closed before the maximum number of requests are processed if the server is too busy or the limit on the idle time or life time is reached. The ip http timeout-policy command allows you to specify a general access policy to the HTTP server by adjusting the connection timeout values. For example, if you want to maximize throughput for HTTP connections, you should configure a policy that minimizes connection overhead. You can do this by specifying large values for the life and requests options so that each connection stays open longer and more requests are processed for each connection. Another example would be to configure a policy that minimizes the response time for new connections. You can do this by specifying small values for the life and requests options so that the connections are quickly released to serve new clients. A throughput policy would be better for HTTP sessions with dedicated management applications, as it would allow the application to send more requests before the connection is closed, while a response time policy would be better for interactive HTTP sessions, as it would allow more people to connect to the server at the same time without having to wait for connections to become available. In general, you should configure these options as appropriate for your environment. The value for the idle option should be balanced so that it is large enough not to cause an unwanted request or response timeout on the connection, but small enough that it does not hold a connection open longer than necessary. ExamplesIn the following example, a Throughput timeout policy is applied. This configuration would allow each connection to be idle for a maximum of 30 seconds (approximately). Each connection will remain open (be âaliveâ) until either the HTTP server has been busy processing requests for approximately 2 minutes (120 seconds) or until approximately 100 requests have been processed.
Router(config)# ip http timeout-policy idle 30 life 120 requests 100
In the following example, a Response Time timeout policy is applied. This configuration would allow each connection to be idle for a maximum of 30 seconds (approximately). Each connection will be closed as soon as the first request has been processed.
Router(config)# ip http timeout-policy idle 30 life 30 requests 1
show ip http clientTo display a report about the HTTP client, use the show ip http client command in user EXEC or privileged EXEC mode.
show
ip
http
client
{all | cache | connection | history | secure status | session-module | statistics}
Syntax Description
Command History
Usage GuidelinesUse this command to display information about the HTTP client.
ExamplesThe following is sample output from the show ip http client cache command:
Router# show ip http client cache
HTTP client cache:
Maximum Memory size for cache : 100000 bytes (default)
Maximum memory per cache entry : 2000 bytes (default)
Memory used : 1381 bytes
Memory Available : 98619 bytes
Cache Ager interval : 5 minutes (default)
Total entries created : 2
Id Type Url Memory-size(Bytes) Refcnt Valid(Sec)
__________________________________________________________________________
536 Hdr 172.25.125.69/ 673 0 -1
32 Hdr 172.25.125.7:8888/ 708 0 -1
The report is self-explanatory and lists information about the cache. The following is sample output from the show ip http client connection command:
Router# show ip http client connection
HTTP client current connections:
Persistent connection = enabled (default)
Connection establishment timeout = 10s (default)
Connection idle timeout = 30s (default)
Maximum number of connection establishment retries = 1 (default)
Maximum http client connections per host : 2
HTTP secure client capability: Not present
local-ipaddress:port remote-ipaddress:port in-bytes out-bytes
:80 172.20.67.174:11012 12584 176
Total client connections : 1
The report is self-explanatory and lists the active connections and user-configured or default values for the connections. The following is sample output from the show ip http client history command:
Router# show ip http client history
HTTP client history:
GET 03:25:36 UTC Thu Feb 26 2004
mailer.cisco.com/mailer.html
GET 03:25:56 UTC Thu Feb 26 2004
mailer.cisco.com/mailer.html
GET 03:26:10 UTC Thu Feb 26 2004
mailer.cisco.com/mailer.html
The report is self-explanatory and lists the most recent URLs accessed by the HTTP client. The following is sample output from the show ip http client secure status command:
Router# show ip http client secure status
HTTP secure client ciphersuite: 3des-ede-cbc-sha des-cbc-sha rc4-128-md5 rc4-12a
HTTP secure client trustpoint: TP-1
The table below describes the significant fields shown in the display.
The following is sample output from the show ip http client session-module command:
Router# show ip http client session-module
HTTP client application session modules:
Id :1
Application Name :HTTP CFS
Version :HTTP/1.1
Persistent :non-persistent
Response-timeout :0
Retries :0
Proxy :
Id :6
Application Name :httpc_ifs_0
Version :HTTP/1.1
Persistent :non-persistent
Response-timeout :16
Retries :0
Proxy :
The table below describes the fields shown in the display. Related Commands
show ip http client connectionTo display a report about HTTP client active connections, use the show ip http client connection command in privileged EXEC mode. Usage GuidelinesUse this command to display active connections and configured values for connections. ExamplesThe following is sample output from the show ip http client connection command:
Router# show ip http client connection
HTTP client current connections:
Persistent connection = enabled (default)
Connection establishment timeout = 10s (default)
Connection idle timeout = 30s (default)
Maximum number of connection establishment retries = 1 (default)
Maximum http client connections per host : 2
HTTP secure client capability: Not present
local-ipaddress:port remote-ipaddress:port in-bytes out-bytes
:80 172.20.67.174:11012 12584 176
Total client connections : 1
The report is self-explanatory and lists the active connections and user-configured or default values for the connections. Related Commands
show ip http client cookieTo display the HTTP client cookies, use the show ip http client cookie command in privileged EXEC mode.
show
ip
http
client
cookie
{brief | summary}
[domain cookie-domain | name cookie-name | session session-name]
Syntax Description
ExamplesThe following is example output from the show ip http client cookie briefcommand: Device# show ip http client cookie brief HTTP client cookies of session HTTP CFS : HTTP client cookies of session CWMP_CLIENT : For expanded output please use 'summary' option for display Name Value Ver Domain Path cookie8 8 1 172.17.0.2 /cwmp-1-0/ cookie7 7 1 172.17.0.2 /cwmp-1-0/ cookie3 3 1 172.16.0.2 /cwmp-1-0/ cookie2 2 1 172.16.0.2 /cwmp-1-0/ cookie1 1 1 172.16.0.2 /cwmp-1-0/ HTTP client cookies of session cwmp_test_client : The following is example output from the show ip http client cookie brief domaincommand: Device# show ip http client cookie brief domain 172.16.0.2 HTTP client cookies of domain 172.16.0.2 : For expanded output please use 'summary' option for display Name Value Ver Domain Path cookie3 3 1 172.16.0.2 /cwmp-1-0/ cookie2 2 1 172.16.0.2 /cwmp-1-0/ cookie1 1 1 172.16.0.2 /cwmp-1-0/ The following is example output from the show ip http client cookie brief namecommand: Device# show ip http client cookie brief name cookie3 HTTP client cookies of name cookie3 : For expanded output please use 'summary' option for display Name Value Ver Domain Path cookie3 3 1 172.16.0.2 /cwmp-1-0/ The following is example output from the show ip http client cookie brief sessioncommand: Device# show ip http client cookie brief session CWMP_CLIENT HTTP client cookies of session CWMP_CLIENT : For expanded output please use 'summary' option for display Name Value Ver Domain Path cookie8 8 1 172.17.0.2 /cwmp-1-0/ cookie7 7 1 172.17.0.2 /cwmp-1-0/ cookie3 3 1 172.16.0.2 /cwmp-1-0/ cookie2 2 1 172.16.0.2 /cwmp-1-0/ cookie1 1 1 172.16.0.2 /cwmp-1-0/ The following is example output from the show ip http client cookie summarycommand:
Device# show ip http client cookie summary
HTTP client cookies of session HTTP CFS :
HTTP client cookies of session CWMP_CLIENT :
Name : cookie8
Value : 8
Version : 1
Domain : 172.17.0.2 (default)
Path : /cwmp-1-0/ (default)
Secure : no
Max-Age : 600
Port :
Comment :
CommentURL :
Name : cookie7
Value : 7
Version : 1
Domain : 172.17.0.2 (default)
Path : /cwmp-1-0/ (default)
Secure : no
Max-Age : 600
Port :
Comment :
CommentURL :
Name : cookie3
Value : 3
Version : 1
Domain : 172.16.0.2 (default)
Path : /cwmp-1-0/ (default)
Secure : no
Max-Age : 600
Port :
Comment :
CommentURL :
Name : cookie2
Value : 2
Version : 1
Domain : 172.16.0.2 (default)
Path : /cwmp-1-0/ (default)
Secure : no
Max-Age : 600
Port :
Comment :
CommentURL :
Name : cookie1
Value : 1
Version : 1
Domain : 172.16.0.2 (default)
Path : /cwmp-1-0/ (default)
Secure : no
Max-Age : 600
Port :
Comment :
CommentURL :
HTTP client cookies of session cwmp_test_client :
The following is example output from the show ip http client cookie summary domaincommand: Device# show ip http client cookie summary domain 172.17.0.2 HTTP client cookies of domain 172.17.0.2 : Name : cookie8 Value : 8 Version : 1 Domain : 172.17.0.2 (default) Path : /cwmp-1-0/ (default) Secure : no Max-Age : 600 Port : Comment : CommentURL : Name : cookie7 Value : 7 Version : 1 Domain : 172.17.0.2 (default) Path : /cwmp-1-0/ (default) Secure : no Max-Age : 600 Port : Comment : CommentURL : The following is example output from the show ip http client cookie summary namecommand: Device# show ip http client cookie summary name cookie7 HTTP client cookies of name cookie7 : Name : cookie7 Value : 7 Version : 1 Domain : 172.17.0.2 (default) Path : /cwmp-1-0/ (default) Secure : no Max-Age : 600 Port : Comment : CommentURL : The following is example output from the show ip http client cookie summary sessioncommand:
Device# show ip http client cookie summary session CWMP_CLIENT
HTTP client cookies of session CWMP_CLIENT :
Name : cookie8
Value : 8
Version : 1
Domain : 172.17.0.2 (default)
Path : /cwmp-1-0/ (default)
Secure : no
Max-Age : 600
Port :
Comment :
CommentURL :
Name : cookie7
Value : 7
Version : 1
Domain : 172.17.0.2 (default)
Path : /cwmp-1-0/ (default)
Secure : no
Max-Age : 600
Port :
Comment :
CommentURL :
Name : cookie3
Value : 3
Version : 1
Domain : 172.16.0.2 (default)
Path : /cwmp-1-0/ (default)
Secure : no
Max-Age : 600
Port :
Comment :
CommentURL :
Name : cookie2
Value : 2
Version : 1
Domain : 172.16.0.2 (default)
Path : /cwmp-1-0/ (default)
Secure : no
Max-Age : 600
Port :
Comment :
CommentURL :
Name : cookie1
Value : 1
Version : 1
Domain : 172.16.0.2 (default)
Path : /cwmp-1-0/ (default)
Secure : no
Max-Age : 600
Port :
Comment :
CommentURL :
show ip http client historyTo display up to 20 URLs accessed by the HTTP client, use the show ip http client history command in privileged EXEC mode. Usage GuidelinesThis command displays a list of up to 20 URLs most recently accessed by the HTTP client. ExamplesThe following is sample output from the show ip http client history command:
Router# show ip http client history
HTTP client history:
GET 03:25:36 UTC Thu Feb 26 2004
mailer.cisco.com/mailer.html
GET 03:25:56 UTC Thu Feb 26 2004
mailer.cisco.com/mailer.html
GET 03:26:10 UTC Thu Feb 26 2004
mailer.cisco.com/mailer.html
The report is self-explanatory and lists the most recent URLs accessed by the HTTP client. Related Commands
show ip http client secure statusTo display the status of the secure HTTP client configuration, use the show ip http client secure status command in privileged EXEC mode. ExamplesThe following is sample output from the show ip http client secure status command:
Router# show ip http client secure status
HTTP secure client ciphersuite: 3des-ede-cbc-sha des-cbc-sha rc4-128-md5 rc4-12a
HTTP secure client trustpoint: TP-1
The table below describes the significant fields shown in the display. Related Commands
show ip http client session-moduleTo display a report about sessions or applications that have registered with the HTTP client, use the show ip http client session-module command in privileged EXEC mode. Usage GuidelinesUse this command to display information about applications that have registered with the HTTP client. ExamplesThe following is sample output from the show ip http client session-module command:
Router# show ip http client session-module
HTTP client application session modules:
Id :1
Application Name :HTTP CFS
Version :HTTP/1.0
Persistent :non-persistent
Response-timeout :0
Retries :0
Proxy :
Id :6
Application Name :httpc_ifs_0
Version :HTTP/1.1
Persistent :non-persistent
Response-timeout :16
Retries :0
Proxy :
The table below describes the fields shown in the display.
Related Commands
show ip http help-pathTo display the current complete configured path of help files for use by the userâs current GUI screen, use the show ip http help-path command in user EXEC or privileged EXEC mode. Usage GuidelinesUse this command to display the current complete help path configured in the HTTP server. This path is expected to hold help files relating to the userâs current GUI screen. show ip http serverTo display details about the current configuration of the HTTP server, use the show ip http server command in user EXEC or privileged EXEC mode. Syntax Description
Usage GuidelinesUse this command to show detailed status information about the HTTP server. If the HTTP secure server capability is present, the output of the show ip http server all command will also include the information found in the output of the show ip http server secure status command.
ExamplesThe following is sample output from the show ip http server all command:
Router# show ip http server all
HTTP server status: Enabled
HTTP server port: 80
HTTP server authentication method: enable
HTTP server access class: 0
HTTP server base path:
Maximum number of concurrent server connections allowed: 5
Server idle time-out: 30 seconds
Server life time-out: 120 seconds
Maximum number of requests allowed on a connection: 2
HTTP secure server capability: Not Present
HTTP server application session modules:
Session module Name Handle Description
Homepage_Server 5 IOS Homepage Server
QDM 2 QOS Device Manager Server
HTTP IFS Server 1 HTTP based IOS File Server
QDM SA 3 QOS Device Manager Signed Applet Server
WEB_EXEC 4 HTTP based IOS EXEC Server
XSM 6 XML Session Manager
VDM 7 VPN Device Manager Server
ITS 8 IOS Telephony Service
ITS_LOCDIR 9 ITS Local Directory Search
HTTP server current connections:
local-ipaddress:port remote-ipaddress:port in-bytes out-bytes
172.19.254.37:80 192.168.254.45:33737 70 2294
HTTP server statistics:
Accepted connections total: 1360
HTTP server history:
local-ipaddress:port remote-ipaddress:port in-bytes out-bytes end-time
172.19.254.37:80 192.168.254.45:63530 60 1596 10:50:00 12/19
The table below describes the significant fields shown in the display.
The following example shows sample output for the show ip http server status command:
Router# show ip http server status
HTTP server status: Disabled
HTTP server port: 80
HTTP server authentication method: enable
HTTP server access class: 0
HTTP server base path:
Maximum number of concurrent server connections allowed: 5
Server idle time-out: 600 seconds
Server life time-out: 600 seconds
Maximum number of requests allowed on a connection: 1
HTTP secure server capability: Present
HTTP secure server status: Disabled
HTTP secure server port: 443
HTTP secure server ciphersuite: 3des-ede-cbc-sha des-cbc-sha rc4-128-md5 rc4-12a
HTTP secure server client authentication: Disabled
HTTP secure server trustpoint:
The lines indicating the status of the HTTP secure (HTTPS) server will only be visible if your software image supports the HTTPS server. If your software image does not support SSL, only the following line will be visible: HTTP secure server capability: Not present Related Commands
show ip http server secure statusTo display the status of the HTTP secure server configuration, use the show ip http server secure status command in privileged EXEC mode. ExamplesThe following is sample output from the show ip http server secure status command:
Router# show ip http server secure status
HTTP secure server status: Enabled
HTTP secure server port: 1025
HTTP secure server ciphersuite: rc4-128-sha rc4-128-md5
HTTP secure server client authentication: Disabled
HTTP secure server trustpoint: CA-trust-local
The table below describes the significant fields shown in the display.
Related Commands
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|