McAfee MAP-3300-SWG Product Guide - Page 168

Protocol details, Table 149, Option definitions

Page 168 highlights

Overview of Web features Web Configuration Table 149 Option definitions Option Denied Request Headers and Denied Response Headers Definition Specifies a variety of headers to be denied. For example, the Accept-Ranges response means that the server is offering to send data in several parts to the clients. By default, the appliance blocks the Accept-Ranges response header because the server is advertising that it can send data to the clients in several parts. The appliance cannot scan partial files properly, so the appliance removes this header to maintain good security. Add VIA headers to Specifies headers, which are intended to: • Track messages forwards. • Avoid request loops. • Identify the protocol capabilities of all senders along the request/response chain. The Via general-header field is used by gateways and proxies to indicate the intermediate protocols and recipients between the client and the server on requests, and between the original server and the client on responses. Protocol details Table 150 Option definitions Option Display NTLM failure messages Definition Some clients and servers use the Microsoft Windows NT LAN Manager (NTLM) authentication protocol for the secure transmission of credentials, including passwords. Sometimes, the NTLM authentication process fails. For example, if a client using a web browser configured to operate in proxy mode tries to connect via the appliance to a server that requires NTLM authentication, the authentication fails. Forward non-compliant POST requests A POST request is a request made by an HTTP client to send data to a server. A non-compliant POST request occurs when the client (web browser) appends non-compliant characters, such as line breaks, to the POST request. Such malformed requests might be part of an attack on a web server. Default value is Off. Maximum requests per persistent connection Downgrade to HTTP v1.0 TRACE and OPTIONS requests Specifies the maximum number of requests that can be made through the same connection before the appliance drops the connection. Default value is 256. Some clients and servers support HTTP version 1.0 only. The appliance supports HTTP version 1.1 protocol. To communicate with older clients and servers, the appliance can be configured to use HTTP version 1.0 when dealing with HTTP requests or redirections. See the HTTP RFC (2616) for more information. Advanced settings Changing these settings can affect scanning performance. If you are not sure about the impact of making any changes, ask your network expert. Server for internal information pages Authentication types not requiring persistence If several appliances are in use, specifies which appliance to use for authentication. This field is normally blank, and therefore this appliance is used. These settings are required for NTLM. These settings are not required for Kerberos. 168 McAfee Email and Web Security Appliances 5.6.0 Product Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336

Table 149
Option definitions
Option
Definition
Denied Request
Headers
and
Denied Response
Headers
Specifies a variety of headers to be denied.
For example, the
Accept-Ranges
response means that the server is offering to send
data in several parts to the clients.
By default, the appliance blocks the
Accept-Ranges
response header because the
server is advertising that it can send data to the clients
in several parts
. The
appliance cannot scan partial files properly, so the appliance removes this header to
maintain good security.
Add VIA headers to
Specifies headers, which are intended to:
Track messages forwards.
Avoid request loops.
Identify the protocol capabilities of all senders along the request/response chain.
The Via general-header field is used by gateways and proxies to indicate the
intermediate protocols and recipients between the client and the server on
requests, and between the original server and the client on responses.
Protocol details
Table 150
Option definitions
Option
Definition
Display NTLM failure
messages
Some clients and servers use the Microsoft Windows NT LAN Manager (NTLM)
authentication protocol for the secure transmission of credentials, including
passwords.
Sometimes, the NTLM authentication process fails. For example, if a client
using a web browser configured to operate in proxy mode tries to connect via
the appliance to a server that requires NTLM authentication, the authentication
fails.
Forward non-compliant
POST requests
A POST request is a request made by an HTTP client to send data to a server.
A non-compliant POST request occurs when the client (web browser) appends
non-compliant characters, such as line breaks, to the POST request. Such
malformed requests might be part of an attack on a web server. Default value
is Off.
Maximum requests per
persistent connection
Specifies the maximum number of requests that can be made through the
same connection before the appliance drops the connection. Default value is 256.
Downgrade to HTTP v1.0
Some clients and servers support HTTP version 1.0 only. The appliance
supports HTTP version 1.1 protocol. To communicate with older clients and
servers, the appliance can be configured to use HTTP version 1.0 when dealing
with HTTP requests or redirections.
TRACE and OPTIONS
requests
See the HTTP RFC (2616) for more information.
Advanced settings
Changing these settings can affect scanning performance. If you are not sure
about the impact of making any changes, ask your network expert.
Server for internal
information pages
If several appliances are in use, specifies which appliance to use for
authentication. This field is normally blank, and therefore this appliance is used.
Authentication types not
requiring persistence
These settings are required for NTLM.
These settings are not required for Kerberos.
Overview of Web features
Web Configuration
168
McAfee Email and Web Security Appliances 5.6.0 Product Guide