The HTTP Inspection feature in IWSVA provides policy control based on HTTP methods,
URLs, and HTTP headers.
Web behavior has become more complicated. IT managers face many challenges, like enforcing
browser type policies, blocking large file transfers to save bandwidth, blocking Web
file uploads and blocking Web Distributed Authoring and Versioning (WebDAV) traffic.
These actions are used to protect company data from loss, filter on keywords in headers
and take action, block video uploads, and prevent message posting on social networking
service (SNS) sites.
 |
Note
WebDAV is an application protocol related to HTTP 1.1 that allows clients to transparently
publish and manage resources on the World Wide Web.
Filters identify WebDAV traffic according to HTTP method.
|
HTTP Inspection allows admins to identify behavior and filter web traffic according
to HTTP methods, URLs, and headers. It also allows admins to create filters or use
default filters to identify web traffic. After the traffic is identified, IWSVA can
control it according to policy settings that allow admins to determine the appropriate
actions for specific traffic.
|
Note
HTTP Inspection filters cannot inspect the data payload of the HTTP packets. For
example, it cannot look for pattern matching inside the text or file of a webmail
or social networking site post. It can only identify that a POST action is happening
to a defined site or set of sites and prevent that POST.
|
Information about HTTP Inspection is shown in corresponding logs and reports. HTTP
Inspection notifications are also available to inform end-users why their actions
on the Web are being blocked.
See also:
