|
|
You can override a variety of settings that control CTE operation by changing default values in the Advanced tab of the CTE Administration Tool.
The following sections describe how to configure CTE operation:
The default URL is the URL that the CTE will proxy if you attempt to access the CTE directly. For example, if a device user requests http:// CTEIPaddress, the CTE will proxy the URL specified in the Default URL field. You might want to set a default URL if you have your own portal page and the CTE is operating as the default gateway.
To change the Default URL setting for one or both interfaces, go to the Advanced > General screen of the CTE Administration Tool.
When the CTE is configured with a server load balancer, you can specify the outbound request target by setting the SLB Mode and Default Host, as follows:
You can set the Default Host to one of multiple virtual IPs (VIPs) on the SLB or to the domain of the SLB. If the Default Host is a VIP, the CTE will make its requests back to the SLB. For example, if a device user requests http:// SLB_IP_Address/directory/file.html, the CTE will request http:// HostFieldValue/directory/file.html. The HostFieldValue will be identical to SLB_IP_Address. If the Default Host is the domain of the SLB, requests can be made only to a single VIP on the SLB.
Figure 4-1 and the following steps describe the request process when the SLB Mode setting is selected.
1. A client makes a request to the SLB at www.mysite.com. The request in this example is:
GET /index.html
Host: www.mysite.com
User-Agent: Nokia7110/1.0
2. SLB header parsing determines that the request should be routed through the CTE. The request is:
GET /index.html
Host: www.mysite.com
User-Agent: Nokia7110/1.0
3. The CTE uses the value of the Host field in the header to make a request back to the SLB at www.mysite.com, this time as a desktop browser. The request is:
GET /index.html
Host: www.mysite.com
User-Agent: Mozilla/4.0 ...
To change the SLB Mode and Default Host settings, go to the Advanced > General screen of the CTE Administration Tool.
 |
Note For an introduction to how the CTE handles sessions and connections, refer to the "Connections and Sessions" section. |
The CTE supports the following configuration options to control sessions and connections:
When the maximum session timeout is set and a session has not been active for the specified time period, the CTE terminates the session and wipes the data from the cache. Any session that has been inactive longer than the maximum session timeout will be removed. Data from a terminated session, which includes authentication information and other sensitive data, is physically removed from memory, preventing unauthorized access.
Setting a minimum session time, which is a Quality of Service (QOS) guarantee, protects current users when the CTE has many active sessions. When the active sessions threshold is reached, the CTE denies a new user instead of evicting a current user whose minimum session time has not elapsed.
Suppose that the minimum session time is set for 5 minutes and a user requests information through the CTE every 4 minutes and 59 seconds. That user's session will remain active indefinitely. If the user waits more than 5 minutes between requests, the session becomes unprotected and can be replaced by a new session.
If the minimum session time is not set, the CTE can support the maximum number of sessions. However, not setting a minimum session time creates an environment in which new requests are given priority over existing sessions, and there is no guaranteed stability for any session during busy periods.
If the CTE must proxy secure sites, set security to Force HTTPS. When the CTE receives a request through port 80 for a valid web page, it will issue a temporary redirect to the client so that the connection uses HTTPS on port 443. The address to which the client is redirected is determined by the masquerade host IP address set for the CTE.
To configure session and connection settings, go to the Advanced > General screen of the CTE Administration Tool.
The browser masquerade is the user agent to use for transformed pages. Choose Netscape or Internet Explorer if you need the application server to use logic particular to one of those browser types when serving content to a device.
Choose Cisco Content Transformation Engine if you want the CTE to act as its own user agent, which is useful for tracking device traffic for billing or other purposes. If your application server looks for specific user agents, this setting may cause undesirable behavior.
To change the Browser Masquerade setting, go to the Advanced > General screen of the CTE Administration Tool.
The CTE automatically detects the input encoding of the data that it receives. If the data does not specify the input encoding, the CTE uses the input encoding set through the Administration Tool. We recommend that you use Latin-1 encoding for HTML pages and UTF-8 encoding for XML pages. Only one default input encoding format can be active at a time.
|
Note Output encoding, the formats into which information sent from the CTE can be written, is a setting specified in the Device Definition File (DDF) of each device driver. If there is an error in a particular DDF file, each device driver has a hard-coded default value for output encoding. Refer to Chapter 2 of the Design Studio User Guide for output encoding formats. |
To change the Input Character Encoding setting, go to the Advanced > General screen of the CTE Administration Tool.
By default, the CTE proxies all requested applications and web pages, whether or not they have corresponding transformation instructions. You can disable this unrestricted proxy so that the CTE proxies only the applications and web pages it has transformed to prevent access to protected servers that are on the same subnet as the CTE.
To change the Unrestricted Proxy setting, go to the Advanced > General screen of the CTE Administration Tool.
When the CTE proxies a page, it rewrites the HTTP header so that the User-Agent field is changed from the requesting device to a desktop browser. As a result, the request appears to originate with the CTE.
If you need to perform application or web server tracking of each device type initiating requests, you can request that the CTE append an X-Client field to the HTTP header when making an outbound request. The X-Client field of an HTTP header contains the user-agent of the client device that made the original request. You can also request that the CTE append an X-ClientIP field so that you pass through the client device IP address (that is, the IP address of a gateway or proxy server, not of the end device).
For example, a client request to the CTE might be as follows:
GET /index.html
User-Agent: Nokia7110/1.0
When the CTE makes a request to the application server, the X-Client and X-ClientIP fields are added:
GET /index.html
User-Agent: Mozilla/4.0 ...
X-Client: Nokia7110/1.0
X-ClientIP: 192.168.0.1
To change the Client User-Agent Pass-Through or Client IP Pass-Through settings, go to the Advanced > General screen of the CTE Administration Tool.
Some IP phones require a username and password in order to accept data sent to them.
To specify IP phone credentials, perform these steps:
The Advanced > IP Phone screen appears.
Step 2 Specify a username to be used as the default IP phone username.
Step 3 Specify a password to be associated with the default IP phone username.
Step 4 Click Submit.
Posted: Mon Aug 18 15:35:04 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
