HTTP Services Configuration Guide

Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
[Link]
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version
of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
[Link]/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)

© 2016 Cisco Systems, Inc. All rights reserved.

 CONTENTS

CHAPTER 1 Read Me First 1

CHAPTER 2 HTTP/HTTPS 1.1 Web Server and Client 3

Finding Feature Information 3
Information About the HTTP 1.1 Web Server and Client 3
About HTTP/HTTPS Server General Access Policies 4
How to Configure HTTP 1.1 Web Server and Client 5
Configuring the HTTP/HTTPS 1.1 Web Server 5
Configuring the HTTP/HTTPS Client 7
Verifying HTTP/HTTPS Connectivity 9
Configuration Examples for HTTP 1.1 Web Server 9
Configuring the HTTP 1.1 Web Server Example 9
Where to Go Next 10
Additional References 10
Feature Information for the HTTP 1.1 Web Server and Client 12

CHAPTER 3 HTTPS--HTTP Server and Client with SSL 3.0 15

Finding Feature Information 15
Information About HTTPS--HTTP Server and Client with SSL 3.0 15
Secure HTTP Server and Secure HTTP Client 16
Certificate Authority Trustpoints 16
CipherSuites 16
How to Configure the HTTPS--HTTP Server and Client with SSL 3.0 17
Declaring a Certificate Authority Trustpoint 17
Configuring the HTTPS Server with SSL 3.0 20
Verifying the Configuration of the HTTPS Server 23
Providing Additional Security and Efficiency 23
Configuring the HTTPS Client with SSL 3.0 25

HTTP Services Configuration Guide

iii
 Contents

Configuration Examples for the HTTPS--HTTP Server and Client with SSL 3.0 feature 27
Additional References 28
Feature Information for HTTPS--HTTP Server and Client with SSL 3.0 29
Glossary 31

CHAPTER 4 Nginx/HTTP - Web Security Features 33

Finding Feature Information 33
Information About Nginx/HTTP Web Security Features 33
Verifying the Configured Version 34
Additional References 35
Feature Information for Nginx/HTTP -- Web Security Features 36

HTTP Services Configuration Guide

iv
 CHAPTER 1
Read Me First
Important Information about Cisco IOS XE 16
Effective Cisco IOS XE Release 3.7.0E (for Catalyst Switching) and Cisco IOS XE Release 3.17S (for
Access and Edge Routing) the two releases evolve (merge) into a single version of converged release—the
Cisco IOS XE 16—providing one release covering the extensive range of access and edge products in the
Switching and Routing portfolio.

Note The Feature Information table in the technology configuration guide mentions when a feature was
introduced. It may or may not mention when other platforms were supported for that feature. To determine
if a particular feature is supported on your platform, look at the technology configuration guides posted
on your product landing page. When a technology configuration guide is displayed on your product landing
page, it indicates that the feature is supported on that platform.

HTTP Services Configuration Guide

1
 Read Me First

HTTP Services Configuration Guide

2
 CHAPTER 2
HTTP/HTTPS 1.1 Web Server and Client
The HTTP/HTTPS 1.1 Web Server and Client feature provides a consistent interface for users and applications
by implementing support for HTTP/HTTPS 1.1 in Cisco IOS XE software-based devices.
This module describes the concepts and the tasks related to configuring the HTTP/HTTPS 1.1 Web Server
and Client feature.

• Finding Feature Information, page 3

• Information About the HTTP 1.1 Web Server and Client, page 3
• How to Configure HTTP 1.1 Web Server and Client, page 5
• Configuration Examples for HTTP 1.1 Web Server, page 9
• Where to Go Next, page 10
• Additional References, page 10
• Feature Information for the HTTP 1.1 Web Server and Client, page 12

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to [Link]/go/cfn. An account on [Link] is not required.

Information About the HTTP 1.1 Web Server and Client

This feature updates the Cisco implementation of the Hypertext Transfer Protocol (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.

HTTP Services Configuration Guide

3
 HTTP/HTTPS 1.1 Web Server and Client
About HTTP/HTTPS Server General Access Policies

The Cisco implementation of HTTP 1.1 is backward-compatible with previous Cisco IOS XE 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 (SSIs) and HTML forms has not changed. Additional configuration options,
in the form of the ip http timeout-policy command and the ip http max-connectionscommand, 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:
• Cisco web browser user interface, which uses the Cisco IOS XE Homepage Server, HTTP-based EXEC
Server, and HTTP IOS File System (IFS) Server
• VPN Device Manager (VDM) application, which uses the VDM Server and the XML Session Manager
(XSM)
• QoS Device Manager (QDM) application, which uses the QDM Server
• IP Phone and Cisco IOS XE Telephony Service applications, which use the ITS Local Directory Search
and IOS Telephony Server (ITS)

About HTTP/HTTPS Server General Access Policies

The ip http timeout-policy command allows you to specify general access characteristics for the server by
configuring 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/HTTPS connections,
you should configure a policy that minimizes connection overhead. You can configure this type of 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.
Another example would be to configure a policy that minimizes the response time for new connections. You
can configure this type of policy by specifying small values for the life and request options so that the
connections are quickly released to serve new clients.
A throughput policy would be better for HTTP/HTTPS 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/HTTPS 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.
Access security policies for the HTTP/HTTPS server are configured using the ip http authentication command,
which allows only selective users to access the server, the ip http access-class command, which allows only
selective IP hosts to access the server, and the ip http accounting commands command, which specifies a
particular command accounting method for HTTP/HTTPS server users.

HTTP Services Configuration Guide

4
 HTTP/HTTPS 1.1 Web Server and Client
How to Configure HTTP 1.1 Web Server and Client

How to Configure HTTP 1.1 Web Server and Client

Configuring the HTTP/HTTPS 1.1 Web Server

Perform this task to enable the HTTP/HTTPS server and configure optional server characteristics. The
HTTP/HTTPS server is disabled by default.

Note If you want to configure authentication (step 4), you must configure the authentication type before you
begin configuring the HTTP/HTTPS 1.1 web server.

SUMMARY STEPS

1. enable
2. configure terminal
3. ip http server
4. ip http authentication {aaa | enable | local }
5. ip http accounting commands level {default | named-accounting-method-list}
6. ip http port port-number
7. ip http path url
8. ip http access-class access-list-number
9. ip http max-connections value
10. ip http timeout-policy idle seconds life seconds requests value

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
• Enter your password if prompted.
Example:
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 ip http server Enables the HTTP 1.1 server, including the Cisco web browser user interface.
Note To enable HTTP over Secure Socket Layer (HTTPS) server, use the ip http
Example: secure-server command. Before enabling HTTPS, you must disable the
Device(config)# ip http server standard HTTP server using the no ip http server command. This command
is required to ensure only secure connections to the server.

HTTP Services Configuration Guide

5
 HTTP/HTTPS 1.1 Web Server and Client
Configuring the HTTP/HTTPS 1.1 Web Server

Command or Action Purpose

Step 4 ip http authentication {aaa | (Optional) Specifies the authentication method to be used for login when a client
enable | local } connects to the HTTP/HTTPS server. The methods for authentication are:
• aaa --Indicates that the authentication method used for the AAA login service
Example: (specified by the aaa authentication login default command) should be used
Device(config)# ip http for authentication.
authentication local
• enable --Indicates that the “enable” password should be used for authentication.
(This is the default method.)
• local --Indicates that the login user name, password and privilege level access
combination specified in the local system configuration (by the username
global configuration command) should be used for authentication and
authorization.

Step 5 ip http accounting commands (Optional) Specifies a particular command accounting method for HTTP/HTTPS
level {default | server users.
named-accounting-method-list} Command accounting for HTTP/HTTPS is automatically enabled when
authentication, authorization, and accounting (AAA) is configured on the device. It
Example: is not possible to disable accounting. HTTP/HTTPS will default to using the global
Device(config)# ip http AAA default method list for accounting. The CLI can be used to configure
accounting commands 15 default HTTP/HTTPS to use any predefined AAA method list.
• level --Valid privilege level entries are integers from 0 to 15.
• default --Indicates the default accounting method list configured by the aaa
accounting commands CLI.
• named-accounting-method-list --Indicates the name of the predefined command
accounting method list.

Step 6 ip http port port-number (Optional) Specifies the server port that should be used for HTTP/HTTPS
communication (for example, for the Cisco web browser user interface).
Example:
Device(config)# ip http port
8080

Step 7 ip http path url (Optional) Sets the base HTTP path for HTML files. The base path is used to specify
the location of the HTTP/HTTPS server files (HTML files) on the local system.
Example: Generally, the HTML files are located in system flash memory.

Device(config)# ip http path

slot1:

Step 8 ip http access-class (Optional) Specifies the access list that should be used to allow access to the
access-list-number HTTP/HTTPS server.

Example:
Device(config)# ip http
access-class 20

HTTP Services Configuration Guide

6
 HTTP/HTTPS 1.1 Web Server and Client
Configuring the HTTP/HTTPS Client

Command or Action Purpose

Step 9 ip http max-connections value (Optional) Sets the maximum number of concurrent connections allowed to the
HTTP/HTTPS server. The default value is 5.
Example:
Device(config)# ip http
max-connections 10

Step 10 ip http timeout-policy idle (Optional) Sets the characteristics that determine how long a connection to the
seconds life seconds requests HTTP/HTTPS server should remain open. The characteristics are:
value
• idle --The maximum number of seconds the connection will be kept open if
no data is received or response data cannot be sent out on the connection. Note
Example: that a new value may not take effect on any already existing connections. If
Device(config)# ip http the server is too busy or the limit on the life time or the number of requests is
timeout-policy idle 30 life 120 reached, the connection may be closed sooner. The default value is 180 seconds
requests 100 (3 minutes).
• life --The maximum number of seconds the connection will be kept open, from
the time the connection is established. Note that the new value may not take
effect on any already existing connections. If the server is too busy or the limit
on the idle time or the number of requests is reached, it may close the
connection sooner. Also, since the server will not close the 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. The default
value is 180 seconds (3 minutes). The maximum value is 86400 seconds (24
hours).
• requests --The maximum limit on the number of requests processed on a
persistent connection before it is closed. Note that the new value may not take
effect on already existing connections. If the server is too busy or the limit on
the idle time or the life time is reached, the connection may be closed before
the maximum number of requests are processed. The default value is 1. The
maximum value is 86400.

Configuring the HTTP/HTTPS Client

Perform this task to enable the HTTP/HTTPS client and configure optional client characteristics.
The standard HTTP 1.1 client and the secure HTTP client are always enabled. No commands exist to disable
the HTTP client. For information about configuring optional characteristics for the HTTPS client, see the
HTTPS--HTTP Server and Client with SSL 3.0 feature module.

HTTP Services Configuration Guide

7
 HTTP/HTTPS 1.1 Web Server and Client
Configuring the HTTP/HTTPS Client

SUMMARY STEPS

1. enable
2. configure terminal
3. ip http client cache {ager interval minutes | memory {file file-size-limit | pool pool-size-limit}
4. ip http client connection {forceclose | idle timeout seconds | retry count | timeout seconds}
5. ip http client password password
6. ip http client proxy-server proxy-name proxy-port port-number
7. ip http client response timeout seconds
8. ip http client source-interface type number
9. ip http client username username

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
• Enter your password if prompted.
Example:
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 ip http client cache {ager interval minutes | memory {file Configures HTTP client cache.
file-size-limit | pool pool-size-limit}

Example:
Device(config)# ip http client cache memory file 5

Step 4 ip http client connection {forceclose | idle timeout seconds | Configures an HTTP client connection.
retry count | timeout seconds}

Example:
Device(config)# ip http client connection timeout 10

Step 5 ip http client password password Configures the default password used for
connections to remote HTTP servers.
Example:
Device(config)# ip http client password pswd1

Step 6 ip http client proxy-server proxy-name proxy-port Configures an HTTP proxy server.
port-number

HTTP Services Configuration Guide

8
 HTTP/HTTPS 1.1 Web Server and Client
Verifying HTTP/HTTPS Connectivity

Command or Action Purpose

Example:
Device(config)# ip http client proxy-server server1
proxy-port 52

Step 7 ip http client response timeout seconds Specifies the timeout value, in seconds, that the
HTTP client waits for a response from the server.
Example:
Device(config)# ip http client response timeout 60

Step 8 ip http client source-interface type number Configures a source interface for the HTTP client.

Example:

Step 9 ip http client username username Configures the default username used for
connections to remote HTTP servers.
Example:
Device(config)# ip http client user1

Verifying HTTP/HTTPS Connectivity

To verify remote connectivity to the HTTP/HTTPS server, enter the system IP address in a web browser,
followed by a colon and the appropriate port number (80 is the default port number).
For example, if the system IP address is [Link] and the port number is 8080, enter
[Link] as the URL in a web browser.
If HTTP/HTTPS authentication is configured, a login dialog box will appear. Enter the appropriate username
and password. If the default login authentication method of “enable” is configured, you may leave the username
field blank, and use the “enable” password to log in.
The system home page should appear in your browser.

Configuration Examples for HTTP 1.1 Web Server

Configuring the HTTP 1.1 Web Server Example

The following example shows a typical configuration that enables the server and sets some of the characteristics:

ip http server
ip http authentication aaa
ip http accounting commands 15 default
ip http path flash:

HTTP Services Configuration Guide

9
 HTTP/HTTPS 1.1 Web Server and Client
Where to Go Next

ip access-list standard 20
permit [Link] [Link]
permit [Link] [Link]
permit [Link] [Link]
! (Note: all other access implicitly denied)
end
ip http access-class 10
ip http max-connections 10
ip http accounting commands 1 oneacct
In the following example, a Throughput timeout policy is applied. This configuration would allow each
connection to be idle a maximum of 30 seconds (approximately). Each connection will remain open (be “alive”)
until either the HTTP/HTTPS server has been busy processing requests for approximately 2 minutes (120
seconds) or until approximately100 requests have been processed.

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 a maximum of 30 seconds (approximately). Each connection will be closed as soon as
the first request has been processed.

ip http timeout-policy idle 30 life 30 requests 1

Where to Go Next
For information about secure HTTP connections using Secure Sockets Layer (SSL) 3.0, refer to the
HTTPS--HTTP with SSL 3.0 feature module at:
[Link]

Additional References
Related Documents

Related Topic Document Title

Cisco IOS commands Cisco IOS Master Commands List, All Releases

HTTP commands: complete command syntax, Cisco IOS HTTP Services Command Reference
command mode, command history, defaults, usage
guidelines, and examples

HTTPS
• HTTPS--HTTP with SSL 3.0 feature module
• Firewall Support of HTTPS Authentication
Proxy feature module

HTTP Services Configuration Guide

10
HTTP/HTTPS 1.1 Web Server and Client
Additional References

Standards and RFCs

Standard/RFC Title
No specific standards are supported by this feature. —
Note that HTTP 1.1, as defined in RFC 2616, is
currently classified as a “Standards Track” document
by the IETF.

RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1

The Cisco implementation of the HTTP Version 1.1 supports a subset of elements defined in RFC 2616.
Following is a list of supported RFC 2616 headers:
• Allow (Only GET, HEAD, and POST methods are supported)
• Authorization, WWW-Authenticate - Basic authentication only
• Cache-control
• Chunked Transfer Encoding
• Connection close
• Content-Encoding
• Content-Language
• Content-Length
• Content-Type
• Date, Expires
• Location

MIBs

MIB MIBs Link

To locate and download MIBs for selected platforms,
• No specific MIBs are supported for this feature. Cisco software releases, and feature sets, use Cisco
MIB Locator found at the following URL:
[Link]

HTTP Services Configuration Guide

11
 HTTP/HTTPS 1.1 Web Server and Client
Feature Information for the HTTP 1.1 Web Server and Client

Technical Assistance

Description Link
The Cisco Support and Documentation website [Link]
provides online resources to download documentation,
software, and tools. Use these resources to install and
configure the software and to troubleshoot and resolve
technical issues with Cisco products and technologies.
Access to most tools on the Cisco Support and
Documentation website requires a [Link] user ID
and password.

Feature Information for the HTTP 1.1 Web Server and Client
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to [Link]/go/cfn. An account on [Link] is not required.

HTTP Services Configuration Guide

12
HTTP/HTTPS 1.1 Web Server and Client
Feature Information for the HTTP 1.1 Web Server and Client

Table 1: Feature Information for HTTP 1.1 Web Server and Client

Feature Name Releases Feature Information

HTTP 1.1 Web Server and Client Cisco IOS XE Release 2.1 The HTTP 1.1 Web Server and
Client feature provides a consistent
interface for users and applications
by implementing support for HTTP
1.1 in Cisco IOS XE
software-based devices. When
combined with the HTTPS feature,
the HTTP 1.1 Web Server and
Client feature provides a complete,
secure solution for HTTP services
between Cisco devices.
The following commands were
introduced or modified by this
feature: debug ip http all, debug
ip http client, ip http access-class,
ip http authentication, ip http
client cache, ip http client
connection, ip http client
password, ip http client
proxy-server, ip http client
response timeout, ip http client
source-interface, ip http client
username, ip http
max-connections, ip http path, ip
http port, ip http server, ip http
timeout-policy, show ip http
client, show ip http client
connection, show ip http client
history, show ip http client
session-module, show ip http
server, show ip http server secure
status.

HTTP Services Configuration Guide

13
 HTTP/HTTPS 1.1 Web Server and Client
Feature Information for the HTTP 1.1 Web Server and Client

Feature Name Releases Feature Information

HTTP TACAC+ Accounting Cisco IOS XE Release 2.1 The HTTP TACAC+ Accounting
Support Support feature introduces the ip
http accounting commands
command. This command is used
to specify a particular command
accounting method for HTTP
server users. Command accounting
provides information about the
commands for a specified privilege
level that are being executed on a
device. Each command accounting
record corresponds to one IOS XE
command executed at its respective
privilege level, as well as the date
and time the command was
executed, and the user who
executed it. The following sections
provide information about this
feature:
The following commands were
introduced or modified by this
feature: ip http accounting
commands.

HTTP Security Cisco IOS XE Release 2.1 This feature was introduced on
Cisco ASR 1000 Series Routers.

HTTP Services Configuration Guide

14
 CHAPTER 3
HTTPS--HTTP Server and Client with SSL 3.0
The HTTPS--HTTP Server and Client with SSL 3.0 feature provides Secure Socket Layer (SSL) version 3.0
support for the HTTP 1.1 server and HTTP 1.1 client within Cisco IOS XE software. SSL provides server
authentication, encryption, and message integrity to allow secure HTTP communications. SSL also provides
HTTP client authentication. HTTP over SSL is abbreviated as HTTPS.

• Finding Feature Information, page 15

• Information About HTTPS--HTTP Server and Client with SSL 3.0, page 15
• How to Configure the HTTPS--HTTP Server and Client with SSL 3.0, page 17
• Configuration Examples for the HTTPS--HTTP Server and Client with SSL 3.0 feature, page 27
• Additional References, page 28
• Feature Information for HTTPS--HTTP Server and Client with SSL 3.0, page 29
• Glossary, page 31

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to [Link]/go/cfn. An account on [Link] is not required.

Information About HTTPS--HTTP Server and Client with SSL 3.0

To configure the HTTP with SSL 3.0 (HTTPS) feature, you should understand the following concepts:

HTTP Services Configuration Guide

15
 HTTPS--HTTP Server and Client with SSL 3.0
Secure HTTP Server and Secure HTTP Client

Secure HTTP Server and Secure HTTP Client

A secure HTTP connection means that data sent to and received from an HTTP server are encrypted before
being sent out over the Internet. HTTP with SSL encryption provides a secure connection to allow such
functions as configuring a router from a web browser. Cisco’s implementation of the secure HTTP server and
secure HTTP client uses an implementation of the SSL version 3.0. Application layer encryption provides an
alternative to older methods such as having to set up a tunnel to the HTTP server for remote management.
HTTP over SSL is abbreviated as HTTPS; the URL of a secure connection will begin with https:// instead of
[Link]
The Cisco IOS XE HTTP secure server’s primary role is to listen for HTTPS requests on a designated port
(the default HTTPS port is 443) and to pass the request to the HTTP 1.1 web server. The HTTP 1.1 server
processes requests and passes responses (served pages) back to the HTTP secure server, which, in turn,
responds to the original request.
The Cisco IOS XE HTTP secure client’s primary role is to respond to Cisco IOS XE application requests for
HTTPS User Agent services, perform HTTPS User Agent services on the application’s behalf, and pass the
response back to the application.

Certificate Authority Trustpoints

Certificate authorities (CAs) are responsible for managing certificate requests and issuing certificates to
participating IPSec network devices. These services provide centralized security key and certificate management
for the participating devices. Specific CA servers are referred to as “trustpoints.”
The HTTPS server provides a secure connection by providing a certified X.509v3 certificate to the client
when a connection attempt is made. The certified X.509v3 certificate is obtained from a specified CA trustpoint.
The client (usually a web browser), in turn, has a public key that allows it to authenticate the certificate.
Configuring a CA trustpoint is highly recommended for secure HTTP connections. However, if a CA trustpoint
is not configured for the routing device running the HTTPS server, the server will certify itself and generate
the needed RSA key pair. Because a self-certified (self-signed) certificate does not provide adequate security,
the connecting client will generate a notification that the certificate is self-certified, and the user will have the
opportunity to accept or reject the connection. This option is available for internal network topologies (such
as testing).
The HTTPS--HTTP Server and Client with SSL 3.0 feature also provides an optional command (ip http
secure-client-auth) that, when enabled, has the HTTPS server request an X.509v3 certificate from the client.
Authenticating the client provides more security than server authentication by itself.
For additional information on certificate authorities, see the “Configuring Certification Authority
Interoperability” chapter in the Cisco IOS XE Security Configuration Guide .

CipherSuites
A CipherSuite specifies the encryption algorithm and digest algorithm to use on an SSL connection. Web
browsers offer a list of supported CipherSuites when connecting to the HTTPS server, and the client and
server will negotiate the best encryption algorithm to use from those that are supported by both. For example,
Netscape Communicator 4.76 supports U.S. security with RSA Public Key Cryptography, MD2, MD5,
RC2-CBC, RC4, DES-CBC, and DES-EDE3-CBC.

HTTP Services Configuration Guide

16
 HTTPS--HTTP Server and Client with SSL 3.0
How to Configure the HTTPS--HTTP Server and Client with SSL 3.0

For the best possible encryption, you should use a browser that supports 128-bit encryption, such as Microsoft
Internet Explorer version 5.5 (or later), or Netscape Communicator version 4.76 (or later). The
SSL_RSA_WITH_DES_CBC_SHA CipherSuite provides less security than the other CipherSuites, because
it does not offer 128-bit encryption.
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):
1 SSL_RSA_WITH_DES_CBC_SHA
2 SSL_RSA_WITH_RC4_128_MD5
3 SSL_RSA_WITH_RC4_128_SHA
4 SSL_RSA_WITH_3DES_EDE_CBC_SHA

How to Configure the HTTPS--HTTP Server and Client with SSL

3.0

Declaring a Certificate Authority Trustpoint

Configuring a CA trustpoint is highly recommended for secure HTTP connections. The certified X.509v3
certificate for the secure HTTP server (or client) is obtained from the specified CA trustpoint. If you do not
declare a CA trustpoint, then a self-signed certificate will be used for secure HTTP connections. The self-signed
certificate is generated automatically.

HTTP Services Configuration Guide

17
 HTTPS--HTTP Server and Client with SSL 3.0
Declaring a Certificate Authority Trustpoint

SUMMARY STEPS

1. enable
2. configure terminal
3. hostname name
4. ip domain-name name
5. crypto key generate rsa usage-keys
6. crypto ca trustpoint name
7. enrollment url url
8. enrollment http-proxy host-name port-number
9. crl {query url | optional | best-effort}
10. primary
11. exit
12. crypto ca authenticate name
13. crypto ca enrollment name
14. Do one of the following:
• copy running-config startup-config
•
• copy system:running-config nvram:startup-config

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
• Enter your password if prompted.
Example:
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 hostname name Specifies the hostname of the Device.

• This step is needed only if you have not previously configured a
Example: hostname for your Device. The hostname is required because a fully
Device(config)# hostname Router qualified domain name is needed for security keys and certificates.

Step 4 ip domain-name name Specifies the IP domain name of the Device.

HTTP Services Configuration Guide

18
 HTTPS--HTTP Server and Client with SSL 3.0
Declaring a Certificate Authority Trustpoint

Command or Action Purpose

• This step is needed only if you have not previously configured an IP
Example: domain name for your Device. The domain name is required because
a fully qualified domain name is needed for security keys and
Device(config)# ip domain-name certificates.
[Link]

Step 5 crypto key generate rsa usage-keys (Optional) Generates an RSA key pair.
• The usage-keys keyword specifies that two RSA special-usage key
Example: pairs should be generated (that is, one encryption pair and one signature
Device(config)# crypto key generate pair) instead of one general-purpose key pair.
rsa usage-keys
• RSA key pairs are used to sign and encrypt Internet key exchange
(IKE) key management messages and are required before you can
obtain a certificate for your Device.
• RSA key pairs are generated automatically. This command can be
used to regenerate the keys, if needed.

Note There are other keywords and arguments for this command, but
they do not pertain to this feature.
Step 6 crypto ca trustpoint name Specifies a local configuration name for the CA trustpoint and enters CA
trustpoint configuration mode.
Example: Note The crypto ca identity command was replaced by the crypto ca
Device(config)# crypto ca trustpoint trustpoint command.
TP1

Step 7 enrollment url url Specifies a URL of the CA where your Device should send certificate
requests.
Example: • If you are using Simple Certificate Enrollment Protocol (SCEP) for
Device(ca-trustpoint)# enrollment enrollment, the URL argument must be in the form [Link] ,
url [Link] where CA-name is the host Domain Name System (DNS) name or IP
address of the CA trustpoint.

Step 8 enrollment http-proxy host-name (Optional) Configures the Device to obtain certificates from the CA through
port-number an HTTP proxy server.

Example:
Device(ca-trustpoint)# enrollment
http-proxy [Link] 8080

Step 9 crl {query url | optional | best-effort} Configures the Device to request a certificate revocation list (CRL), make
CRL checking optional, or perform CRL checking on a “best-effort” basis.
Example:
• CRLs ensure that the certificate of the peer has not been revoked.
Device(ca-trustpoint)# crl query
ldap://[Link] • The crl optional command configures the Device to accept certificates
even if the appropriate CRL cannot be downloaded.

HTTP Services Configuration Guide

19
 HTTPS--HTTP Server and Client with SSL 3.0
Configuring the HTTPS Server with SSL 3.0

Command or Action Purpose

• Use the crl query url command to specify the Lightweight Directory
Access Protocol (LDAP) URL of the CA server; for example,
ldap://another-server.

Step 10 primary (Optional) Specifies that this trustpoint should be used as the primary
(default) trustpoint for CA requests.
Example: • Use this command if more than one CA trustpoint will be configured
Device(ca-trustpoint)# primary on this Device.

Step 11 exit Exits CA trustpoint configuration mode and returns to global configuration
mode.
Example:
Device(ca-trustpoint)# exit

Step 12 crypto ca authenticate name Authenticates the CA by getting the public key of the CA.
• Use the same name that you used when declaring the CA in the crypto
Example: ca trustpoint command.
Device(config)# crypto ca
authenticate TP1

Step 13 crypto ca enrollment name Obtains the certificate from the specified CA trustpoint.
• This command requests a signed certificate from the CA for each RSA
Example: key pair.
Device(config)# crypto ca enrollment
TP1

Step 14 Do one of the following: Saves the configuration to NVRAM.

• copy running-config startup-config • This command is required to save the certificates into NVRAM. If not
used, the certificates would be lost at Device reload.
•
• copy system:running-config Note To execute EXEC mode commands in global configuration mode,
nvram:startup-config you can add the do keyword before the command. For example,
instead of copy running-config startup-config, you could enter
do copy running-config startup-config.
Example:
Device(config)# copy running-config
startup-config

Configuring the HTTPS Server with SSL 3.0

To disable the standard HTTP server and configure the HTTPS server with SSL 3.0, complete the procedure
in this section.

HTTP Services Configuration Guide

20
 HTTPS--HTTP Server and Client with SSL 3.0
Configuring the HTTPS Server with SSL 3.0

Before You Begin

If a certificate authority is to be used for certification, you should declare the CA trustpoint on the routing
device before enabling the secure HTTP server.

SUMMARY STEPS

1. enable
2. Device# show ip http server status
3. configure terminal
4. no ip http server
5. ip http secure-server
6. ip http secure-port port-number
7. ip http secure-ciphersuite [3des-ede-cbc-sha] [rc4-128-sha] [rc4-128-md5] [des-cbc-sha]
8. ip http secure-client-auth
9. ip http secure-trustpoint name
10. end
11. show ip http server secure status

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
• Enter your password if prompted.
Example:
Device> enable

Step 2 Device# show ip http server status (Optional) Displays the status of the HTTP server.
• If you are unsure whether the secure HTTP server is supported in the
Example: software image you are running, enter this command and look for the
Device# show ip http server status line “HTTP secure server capability: {Present | Not present}”.
• This command displays the status of the standard HTTP server (enabled
Example: or disabled).

Step 3 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 4 no ip http server Disables the standard HTTP server.

Note When enabling the HTTPS server you should always disable the
Example: standard HTTP server to prevent insecure connections to the same
Device(config)# no ip http server services. This is a precautionary step (typically, the HTTP server
is disabled by default).

HTTP Services Configuration Guide

21
 HTTPS--HTTP Server and Client with SSL 3.0
Configuring the HTTPS Server with SSL 3.0

Command or Action Purpose

Step 5 ip http secure-server Enables the HTTPS server.

Example:
Device(config)# ip http
secure-server

Step 6 ip http secure-port port-number (Optional) Specifies the port number that should be used for the HTTPS
server. The default port number is 443. Valid options are 443 or any number
Example: in the range 1025 to 65535.

Device(config)# ip http secure-port

1025

Step 7 ip http secure-ciphersuite (Optional) Specifies the CipherSuites (encryption algorithms) that should
[3des-ede-cbc-sha] [rc4-128-sha] be used for encryption over the HTTPS connection.
[rc4-128-md5] [des-cbc-sha]
• This command allows you to restrict the list of CipherSuites that the
server offers the connecting clients. For example, you may want to
Example: allow only the most secure CipherSuite to be used.
Device(config)# ip http
secure-ciphersuite rc4-128-sha • Unless you have a reason to specify the CipherSuites that should be
rc4-128-md5 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).

Step 8 ip http secure-client-auth (Optional) Configures the HTTP server to request an X.509v3 certificate
from the client in order to authenticate the client during the connection
Example: process.

Device(config)# ip http • In the default connection and authentication process, the client requests
secure-client-auth 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 clients may be
configured for CA authentication.

Step 9 ip http secure-trustpoint name Specifies the CA trustpoint that should be used to obtain an X.509v3 security
certificate and to authenticate the connecting client’s certificate.
Example:
• Use of this command assumes you have already declared a CA
Device(config)# ip http trustpoint using the crypto ca trustpoint command and associated
secure-trustpoint trustpoint-01 submode commands.
• Use the same trustpoint name that you used in the associated crypto
ca trustpoint command.

Step 10 end Ends the current configuration session and returns you to privileged EXEC
mode.
Example:
Device(config)# end

HTTP Services Configuration Guide

22
 HTTPS--HTTP Server and Client with SSL 3.0
Providing Additional Security and Efficiency

Command or Action Purpose

Step 11 show ip http server secure status Displays the status of the HTTP secure server configuration.

Example:
Device# show ip http server secure
status

Verifying the Configuration of the HTTPS Server

To verify the configuration of the HTTPS server, connect to the router running the HTTPS server with a web
browser by entering [Link] , where url is the IP address or hostname of the router. Successful connection
using the https prefix (instead of the standard http) indicates that the HTTPS server is configured properly.
If a port other than the default port is configured (using the ip http secure-port command), you must also
specify the port number after the URL. For example:

[Link]
or

[Link]
Generally, you can verify that the HTTPS server is configured and that you have a secure connection by
locating an image of a padlock at the bottom of your browser window. Also note that secure HTTP connections
have a URL that starts with “https:” instead of “http:”.

Providing Additional Security and Efficiency

The configuration of the standard HTTP server applies to the secure HTTP server as well. To provide additional
security and efficiency to both the standard HTTP server and the HTTPS server, complete the procedure in
this section.

SUMMARY STEPS

1. enable
2. configure terminal
3. ip http path path-name
4. ip http access-class access-list-number
5. ip http max-connections value
6. ip http timeout-policy idle seconds life seconds requests value

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.

HTTP Services Configuration Guide

23
 HTTPS--HTTP Server and Client with SSL 3.0
Providing Additional Security and Efficiency

Command or Action Purpose

• Enter your password if prompted.
Example:
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 ip http path path-name (Optional) Sets the base HTTP path for HTML files.
• The base path is used to specify the location of the HTTP server files (HTML
Example: files) on the local system. Generally, the HTML files are located in system
Device(config)# ip http path flash memory.
slot1:

Step 4 ip http access-class (Optional) Specifies the access list that should be used to allow access to the HTTP
access-list-number server.

Example:
Device(config)# ip http
access-class 20

Step 5 ip http max-connections value (Optional) Sets the maximum number of concurrent connections to the HTTP server
that will be allowed. The default value is 5.
Example:
Device(config)# ip http
max-connections 10

Step 6 ip http timeout-policy idle seconds (Optional) Sets the characteristics that determine how long a connection to the
life seconds requests value HTTP server should remain open. The characteristics are:
• idle --The maximum number of seconds the connection will be kept open if
Example: no data is received or response data cannot be sent out on the connection.
Device(config)# ip http Note that a new value may not take effect on any already existing connections.
timeout-policy idle 30 life 120 If the server is too busy or the limit on the life time or the number of requests
requests 100
is reached, the connection may be closed sooner. The default value is 180
seconds (3 minutes).
• life --The maximum number of seconds the connection will be kept open,
from the time the connection is established. Note that the new value may not
take effect on any already existing connections. If the server is too busy or
the limit on the idle time or the number of requests is reached, it may close
the connection sooner. Also, because the server will not close the 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.

HTTP Services Configuration Guide

24
 HTTPS--HTTP Server and Client with SSL 3.0
Configuring the HTTPS Client with SSL 3.0

Command or Action Purpose

The default value is 180 seconds (3 minutes). The maximum value is 86,400
seconds (24 hours).
• requests --The maximum limit on the number of requests processed on a
persistent connection before it is closed. Note that the new value may not
take effect on any already existing connections. If the server is too busy or
the limit on the idle time or the life time is reached, the connection may be
closed before the maximum number of requests are processed. The default
value is 1. The maximum value is 86,400.

Configuring the HTTPS Client with SSL 3.0

To configure the HTTPS client with SSL 3.0, complete the procedure in this section.

Before You Begin

The standard HTTP client and the secure HTTP client are always enabled.
A certificate authority is required for secure HTTP client certification; the following steps assume that you
have previously declared a CA trustpoint on the routing device. If a CA trustpoint is not configured, and the
remote HTTPS server requires client authentication, connections to the secure HTTP client will fail.

SUMMARY STEPS

1. enable
2. configure terminal
3. ip http client secure-trustpoint trustpoint-name
4. ip http client secure-ciphersuite [3des-ede-cbc-sha] [rc4-128-sha] [rc4-128-md5] [des-cbc-sha]
5. end
6. show ip http client secure status

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
• Enter your password if prompted.
Example:
Device> enable

HTTP Services Configuration Guide

25
 HTTPS--HTTP Server and Client with SSL 3.0
Configuring the HTTPS Client with SSL 3.0

Command or Action Purpose

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 ip http client secure-trustpoint (Optional) Specifies the CA trustpoint that should be used if the remote
trustpoint-name HTTP server requests client authentication.
• Use of this command assumes you have already declared a CA
Example: trustpoint using the crypto ca trustpoint command and associated
Device(config)# ip http client submode commands.
secure-trustpoint trustpoint01
• Use the same trustpoint name that you used in the associated crypto
ca trustpoint command.
• This command is optional if client authentication is not needed, or if
a primary trustpoint has been configured. If the ip http client
secure-trustpoint command is not used, the Device will use the
primary trustpoint, as specified by the primaryCA trustpoint
configuration mode command.

Step 4 ip http client secure-ciphersuite (Optional) Specifies the CipherSuites (encryption algorithms) that should
[3des-ede-cbc-sha] [rc4-128-sha] be used for encryption over the HTTPS connection.
[rc4-128-md5] [des-cbc-sha]
• This command allows you to restrict the list of CipherSuites that the
client offers when connecting to a secure HTTP server. For example,
Example: you may want to allow only the most secure CipherSuites to be used.
Device(config)# ip http client
secure-ciphersuite rc4-128-sha • Unless you have a reason to specify the CipherSuites that should be
rc4-128-md5 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).

Step 5 end Ends the current configuration session and returns to privileged EXEC mode.

Example:
Device(config)# end

Step 6 show ip http client secure status Displays the status of the HTTP secure server configuration.

Example:
Device# show ip http client secure
status

HTTP Services Configuration Guide

26
 HTTPS--HTTP Server and Client with SSL 3.0
Configuration Examples for the HTTPS--HTTP Server and Client with SSL 3.0 feature

Configuration Examples for the HTTPS--HTTP Server and Client

with SSL 3.0 feature
The following example shows a configuration session in which the secure HTTP server is enabled, the port
for the secure HTTP server is configured as 1025, and the remote CA trustpoint server “CA-trust-local” is
used for certification.

Device# 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:
Device# configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

Device(config)# ip http secure-server

Device(config)# ip http client secure-trustpoint CA-trust-local

Device(config)# ip http secure-port 1024

Invalid secure port value.

Device(config)# ip http secure-port 1025

Device(config)# ip http secure-ciphersuite rc4-128-sha rc4-128-md5

Device(config)# end

Device# show ip http server secure status

HTTP secure server status: Enabled

HTTP secure server port: 1025

HTTP secure server ciphersuite: rc4-128-md5 rc4-128-sha

HTTP secure server client authentication: Disabled

HTTP secure server trustpoint: CA-trust-local

In the following example, the CA trustpoint CA-trust-local is specified, and the HTTPS client is configured
to use this trustpoint for client authentication requests:

Device# config terminal

Enter configuration commands, one per line. End with CNTL/Z.
Device(config)# crypto ca trustpoint CA-trust-local

Device(ca-trustpoint)# enrollment url [Link]

Device(ca-trustpoint)# crl query ldap://[Link]

Device(ca-trustpoint)# primary

Device(ca-trustpoint)# exit

HTTP Services Configuration Guide

27
 HTTPS--HTTP Server and Client with SSL 3.0
Additional References

Device(config)# ip http client secure-trustpoint CA-trust-local

Device(config)# end

Device# copy running-config startup-config

Additional References
The following sections provide references related to the HTTPS--HTTP Server and Client with SSL 3.0
feature.

Related Documents

Related Topic Document Title

SSL 3.0 The SSL Protocol Version 3.0
This document is available from various sources
online.

Standard Cisco Web Client HTTP 1.1 Web Client

Standard Cisco Web Server HTTP 1.1 Web Server

Certification Authority Interoperability

• Configuring Certification Authority
Interoperability
• Certificate Autoenrollment
• Certificate Enrollment Enhancements
• Trustpoint CLI
• Source Interface Selection for Outgoing Traffic
with Certificate Authority

Standards

Standard Title
No new or modified standards are supported by this --
feature.

HTTP Services Configuration Guide

28
 HTTPS--HTTP Server and Client with SSL 3.0
Feature Information for HTTPS--HTTP Server and Client with SSL 3.0

Related MIBs

MIBs MIBs Link

To locate and download MIBs for selected platforms,
• No new or modified MIBs are supported by this Cisco IOS XE releases, and feature sets, use Cisco
feature and support for existing MIBs has not MIB Locator found at the following URL:
been modified by this feature.
[Link]

Related RFCs

RFCs Description
RFC 2616 Cisco’s implementation of HTTP is based on RFC
2616: Hypertext Transfer Protocol -- HTTP/1.1 .

Technical Assistance

Description Link
The Cisco Support website provides extensive online [Link]
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a [Link] user ID and password.

Feature Information for HTTPS--HTTP Server and Client with

SSL 3.0
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to [Link]/go/cfn. An account on [Link] is not required.

HTTP Services Configuration Guide

29
 HTTPS--HTTP Server and Client with SSL 3.0
Feature Information for HTTPS--HTTP Server and Client with SSL 3.0

Table 2: Feature Information for HTTPS--HTTP Server and Client with SSL 3.0

Feature Name Releases Feature Information

HTTPS--HTTP Server and Client Cisco IOS XE Release 2.1 This feature provides Secure
with SSL 3.0 Socket Layer (SSL) version 3.0
support for the HTTP 1.1 server
and HTTP 1.1 client within Cisco
IOS XE software. SSL provides
server authentication, encryption,
and message integrity to allow
secure HTTP communications.
SSL also provides HTTP client
authentication.
This feature is supported only in
Cisco software images that support
SSL. Specifically, SSL is supported
in “IPSec 56” and “IPSec 3DES”
images (contains “k8” or “k9” in the
image name).
The following commands are
introduced or modified in the
feature or features documented in
this module.
• debug ip http ssl error
• ip http client
secure-ciphersuite
• ip http client
secure-trustpoint
• ip http secure-ciphersuite
• ip http secure-client-auth
• ip http secure-port
• ip http secure-server
• ip http secure-trustpoint
• show ip http client secure
status
• show ip http server secure
status

HTTP Services Configuration Guide

30
 HTTPS--HTTP Server and Client with SSL 3.0
Glossary

Glossary
RSA--RSA is a widely used Internet encryption and authentication system that uses public and private keys
for encryption and decryption. The RSA algorithm was invented in 1978 by Ron Rivest, Adi Shamir, and
Leonard Adleman. The abbreviation RSA comes from the first letter of the last names of the three original
developers. The RSA algorithm is included in many applications, such as the web browsers from Microsoft
and Netscape. The RSA encryption system is owned by RSA Security.
SHA --The Secure Hash Algorithm. SHA was developed by NIST and is specified in the Secure Hash Standard
(SHS, FIPS 180). Often used as an alternative to Digest 5 algorithm.
signatures, digital--In the context of SSL, “signing” means to encrypt with a private key. In digital signing,
one-way hash functions are used as input for a signing algorithm. In RSA signing, a 36-byte structure of two
hashes (one SHA and one MD5) is signed (encrypted with the private key).
SSL 3.0--Secure Socket Layer version 3.0. SSL is a security protocol that provides communications privacy
over the Internet. The protocol allows client and server applications to communicate in a way that is designed
to prevent eavesdropping, tampering, or message forgery. SSL uses a program layer located between the
Internet’s HTTP and TCP layers. SSL is included as part of most web server products and as part of most
Internet browsers.

HTTP Services Configuration Guide

31
 HTTPS--HTTP Server and Client with SSL 3.0
Glossary

HTTP Services Configuration Guide

32
 CHAPTER 4
Nginx/HTTP - Web Security Features
For the Cisco IOS XE Everest 16.4.1 release, the following web security enhancements have been included:
• SSL/TLS Version for HTTP secure-server can be specified.
• Security headers enhancements

• Finding Feature Information, page 33

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to [Link]/go/cfn. An account on [Link] is not required.

Information About Nginx/HTTP Web Security Features

• SSL/TLS Version for HTTP secure-server -- This enhancement is used to specify the TLS version to
be used for HTTPS Server and HTTPS client sessions.
• HTTPS Server command -- By default, it supports three versions. If you want to use a particular
version for the sessions, you can specify by configuring the ip http tls-version command in global
configuration mode. The versions are TLSv1.0, TLSv1.1, and TLSv1.2.
• HTTPS Client command -- By default, it supports three versions. If you want to use a particular
version for the sessions, you can specify by configuring the ip http client tls-version command
in global configuration mode. The versions are TLSv1.0, TLSv1.1, and TLSv1.2.

HTTP Services Configuration Guide

33
 Nginx/HTTP - Web Security Features
Verifying the Configured Version

Note These commands allow you to set the particular version used for sessions. The underlying SSL infrastructure
supports the option of specifying either all or only one TLS version. Hence the HTTPS provides the option
to specify the individual version. Use the no form of the command to remove the configuration.

• Security Header Enhancements

◦HTTP Server – The following headers are the web server security enhancements. The actual headers
and respective values appear in the response by default:
X-XSS-Protection: 1; mode=block -- This header indicates that XSS protection is enabled [ value
1 ] and if the browser finds any attack, it should block rendering the page.
X-Frame-Options: SAMEORIGIN - Allows the contents to be rendered in a frame if it belongs to
the same domain.
X-Content-Type-Options: nosniff - Prevents the browser from doing MIME-type sniffing.
Strict-Transport-Security: max-age=7884000 - Strict-Transport-Security HTTP header. Use the
[no] ip http HSTS-Header to enable/disable this header for IOS applications. By default, it is
enabled and use the no ip http HSTS-Header command disable this header from the response.
◦Nginx – Web user interface - Nginx applications take care of the headers for their response. As
Web UI is one of the NginX application, it adds the security headers. The three headers are the
following:
◦X-XSS-Protection: 1; mode=block
◦X-Frame-Options: SAMEORIGIN
◦X-Content-Type-Options: nosniff

Verifying the Configured Version

Use the show ip http client all command to see the currently enabled TLS version.
Device# show ip http client all

<snip>

Maximum number of requests allowed on a connection: 25

Server linger time : 60 seconds
HTTP server active session modules: ALL
HTTP secure server capability: Present
HTTP secure server status: Enabled
HTTP secure server port: 443
HTTP secure server ciphersuite: 3des-ede-cbc-sha aes-128-cbc-sha
aes-256-cbc-sha dhe-aes-128-cbc-sha ecdhe-rsa-3des-ede-cbc-sha
HTTP secure server TLS version: TLSv1.2 TLSv1.1 TLSv1.0 <<<This line shows the TLS version
that is enabled.
HTTP secure server client authentication: Disabled
HTTP secure server trustpoint:
HTTP secure server active session modules: ALL

<snip>
Use the show http server status command to see the currently enabled TLS version.
Device# show http server status

<snip>

HTTP Services Configuration Guide

34
 Nginx/HTTP - Web Security Features
Additional References

Maximum number of concurrent server connections allowed: 50

Maximum number of secondary server connections allowed: 50
Server idle time-out: 180 seconds
Server life time-out: 180 seconds
Server session idle time-out: 180 seconds
Maximum number of requests allowed on a connection: 25
Server linger time : 60 seconds
HTTP server active session modules: ALL
HTTP secure server capability: Present
HTTP secure server status: Enabled
HTTP secure server port: 443
HTTP secure server ciphersuite: 3des-ede-cbc-sha aes-128-cbc-sha
aes-256-cbc-sha dhe-aes-128-cbc-sha ecdhe-rsa-3des-ede-cbc-sha
HTTP secure server TLS version: TLSv1.2 TLSv1.1 TLSv1.0 <<<This line shows the TLS version
that is enabled.
HTTP secure server client authentication: Disabled
HTTP secure server trustpoint:

<snip>

Additional References
Related Documents

Related Topic Document Title

Additional HTTP configuration information Using the Cisco Web Browser User Interface

Additional HTTPS configuration information HTTPS - HTTP Server and Client with SSL 3.0

Additional HTTP and HTTPS commands Cisco IOS Network Management Command Reference

Technical Assistance

Description Link
The Cisco Support website provides extensive online [Link]
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a [Link] user ID and password.

HTTP Services Configuration Guide

35
 Nginx/HTTP - Web Security Features
Feature Information for Nginx/HTTP -- Web Security Features

Feature Information for Nginx/HTTP -- Web Security Features

The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to [Link]/go/cfn. An account on [Link] is not required.

Table 3: Feature Information for Nginx/HTTP -- Web Security Features

Feature Name Releases Feature Information

Nginx/HTTP -- Web Security Cisco IOS XE Everest 16.4.1 For the Cisco IOS XE Everest
Features Release 16.4.1 release, the following web
security enhancements have been
included:
• SSL/TLS Version for HTTP
secure-server can be
specified.
• Security headers
enhancements

HTTP Services Configuration Guide

36