12.07.2015 Views

WSM User Guide - WatchGuard Technologies

WSM User Guide - WatchGuard Technologies

WSM User Guide - WatchGuard Technologies

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring the HTTP Proxyauthentication methods that the web server accepts. With a default configuration, the Firebox allowsBasic, Digest, NTLM, and Passport1.4 authentication, and strips all other authentication.1 From the Categories section, select Authorization.2 Do the steps used to create rules. For more information, see “Defining Rules” on page 79.Configuring general settings for HTTP responsesYou use the General Settings fields to configure basic HTTP parameters such as idle time-out and limitsfor line and total length. If you set a check box to 0 bytes, the Firebox does not check the parameter.1 From the Categories section, select General Settings.2 To set limits for HTTP parameters, select the applicable check boxes. Use the arrows to set the limits:Idle timeoutControls how long the Firebox HTTP proxy waits for the web server to send the web page. Thedefault value is 600 seconds.Maximum line lengthControls the maximum allowed length of a line of characters in the HTTP response headers. Usethis property to protect your computers from buffer overflow exploits.Maximum total lengthControls the maximum length of the HTTP response headers. If the total header length is morethan this limit, the HTTP response is denied. The default value is 0 (no limit).Setting header fields for HTTP responsesThis property controls which HTTP response header fields the Firebox allows. RFC 2616 includes many ofthe HTTP response headers that are allowed in the default configuration. For more information, see:http://www.ietf.org/rfc/rfc2616.txt1 From the Categories section, select Header Fields.2 Do the steps used to create rules. For more information, see “Defining Rules” on page 161.Setting content types for HTTP responsesWhen a web server sends HTTP traffic, it usually adds a MIME type to the response. The HTTP header onthe data stream contains this MIME type. It is added before the data is sent.This ruleset sets rules for looking for content type (MIME type) in HTTP response headers. By default theFirebox allows some safe content types, and denies MIME content that has no specified content type.Some web servers supply incorrect MIME types to get around content rules.1 From the Categories section, select Content Types.2 Do the steps used to create rulesets. For more information, see “Defining Rules” on page 161.Setting cookies for HTTP responsesHTTP cookies are small files of alphanumeric text put by web servers on web clients. Cookies monitorthe page a web client is on to enable the web server to send more pages in the correct sequence. Webservers also use cookies to collect information about an end user. Many web sites use cookies forauthentication and other legitimate functions and cannot operate correctly without cookies.<strong>User</strong> <strong>Guide</strong> 177

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!