Centro de Excelencia Temprana en Múnich

HTTP general configuration options are options related to a variety of settings such as timeout values, redirection handling, session recognition, multi-frame page handling, and cookie handling. They can be set globally for the AMD or individually for particular software services.

Before You Begin

It is assumed for this task that you have already created one or more user-defined software services for this protocol and know how to access and modify global settings for an AMD and settings for a specific service.

To configure general options for monitoring this protocol:

1. Start and log on to RUM Console.

2. Select Devices and Connections ➤ Manage Devices from the top menu, to display the current device list.

3. Select Open Configuration from the context menu for an AMD. The AMD Configuration window appears.

4. Click Edit as Draft to set your configuration to draft mode (if you are not in draft mode already).

5. Navigate to Front-End-Monitoring ➤ Web ➤ HTTP ➤ General. NOTE

Configuration options related to general settings for an AMD for this protocol analyzer are also under the HTTP Options tab for individual user-defined services.

6. Configure options available in the General section. The list of configuration options includes:

Redirect timeout

This timeout period, expressed in seconds, is configured globally for all software services.

HTTP redirects are stored until either a matching target URL is seen or a timeout expires. If the redirect target page has not been seen by the time the redirect timeout expires, the AMD reports the URL with all transactional metrics equal to zero and the redirect is referred to as an orphaned redirect. The URL reported is taken from the orphaned redirect.

Cascaded unauthorized hits timeout

Cascaded unauthorized hits older or equal to this timeout (in seconds) are treated as unauthorized. In case of a mixed cascade, redirects and unauthorized hits, the head of cascade determines which timeout should be used, Redirect timeout or Cascaded

unauthorized hits timeout. Last packet HTTP session timeout

If the time since the last packet for an HTTP session is longer than this value (in seconds), the hit is considered finished and closed. This timeout period is configured globally for all software services.

Hit session timeout

Maximum time delay allowing a hit to be linked to a page. The value is specified in seconds, with a resolution of one-tenth of a second, and is configured globally for all software services.

User agent timeout

Time in minutes after which a user agent will be erased from the cache. The value is configured globally for all software services.

Maximum header length

Maximum size in bytes of the buffer that the HTTP header can be assembled into before considering it incomplete and proceeding with its processing. This option is available only in HTTP mode of the HTTP analyzer. The value is configured globally for all software services.

Maximum request body length

Maximum size in bytes of the buffer that HTTP request body can be assembled into before considering it incomplete and proceeding with its processing. This option is available only in HTTP mode of the HTTP analyzer. The value is configured globally for all software services.

Report URL after redirect

This option causes addresses after the last redirection to be reported for redirected pages. By default, redirections are reported as addresses of the originating page, before redirection takes place. The final target page will be reported regardless of how many redirects are detected in between.

The option can be set globally for all software services or configured for a specific user-defined software service. Specific settings take precedence over global settings. It is not supported by HTTP Express analyzer.

Report URL prefixed with analyzed HTTP method

If this option is selected, the string “POST” or “GET” is prefixed to the reported URL. This option can be set globally for all software services or configured for a specific user-defined software service. Specific settings take precedence over global settings. The All methods option allows for processing all detected HTTP methods including the WebDAV HTTP extesion. The extended WebDAV methods automatically identified include:

• PROPFIND

Retrieves properties and a directory hierarchy of a remote system.

• PROPPATCH

Changes and deletes multiple properties is a single operation.

• MKCOL

Creates directories or collections. • COPY

Copies a resource from one URI to another. • MOVE

Moves a resource from one URI to another. • LOCK

Puts a lock on a resource.

• UNLOCK

Removes a lock from a resource. NOTE

Monitoring WebDAV software services requires a specific configuration options. In order to properly report a hit as a separate operation, you must define a URL with regex matching all URLs (http://.*) and content types.

Treat a client RST packet sent by the session as closing session

If this option is selected, the protocol analyzer will treat a client RST packet sent by the session as closing the session instead of aborting it if there was no content length header. It is configured globally for all software services.

7. Configure page and session recognition based on cookies

You can use cookies to distinguish between separate HTTP pages and sessions. This is useful when, for example, a number of distinct users are hidden behind a shared load balancer or a proxy server.For more information, see Global Settings for Page and Session Recognition Based on Cookies [p. 118].

8. Select client IP address extraction method.

• To turn off automatic client IP address extraction, select Off.

• To extract the client IP address from a header tag, select Header tag and type the name of the HTTP header field containing the real client IP information.

• The string extracted by the regular expression becomes the real client IP address reported to the report server.

Example 6.

The following is an example of extracting the value of REMOTE_ADDR field from the

HTTP header.

An HTTP header might contain the following information:

GET http://www.slow-server.com/login.jsp HTTP/1.1 Accept: */*

Referer: http://www.slow-server.com/ Accept-Language: en-us

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) Host: www.slow-server.com

Connection: Keep-Alive

Cookie: FPB=061j8hura11q56cv; CRZY9=t=1; REMOTE_ADDR: 10.1.0.2

The following regular expression extracts the address 10.1.0.2 from the REMOTE_ADDR

field:

REMOTE_ADDR: ([.0-9]*)

For details on how expressions are used, see Using Regular Expressions to Extract User Identification in the Data Center Real User Monitoring Web Application Monitoring User Guide.

• To use the real client IP address as both the user ID and the user IP address, select Try

to convert user name to IP address. 9. Save or publish the configuration.

• Click Save to save your changes and continue with configuration.

• Click Save and Publish to immediately update the devices configuration.