Difference between revisions of "Response Types"

From Secure Web Gateway
Share/Save/Bookmark
Jump to: navigation, search
Line 2: Line 2:
 
= Overview =
 
= Overview =
  
Use Response profiles to manage profiling based on the responses received from the webserver.
+
Use Response profiles to manage profiling based on the responses received from the webserver.<br/> You can manage&nbsp;Profiling based on the following parameters present in the responses received from the webserver.
 
 
Profiling can be managed based on the following parameters present in the responses received from the webserver.
 
  
 
*Mime  
 
*Mime  
Line 11: Line 9:
 
*Response header pattern, etc.,  
 
*Response header pattern, etc.,  
  
{| style="width: 100%" cellspacing="1" cellpadding="1" border="0"
+
{| border="0" cellpadding="1" cellspacing="1" style="width: 100%"
 
|-
 
|-
 
| style="width: 957px" |  
 
| style="width: 957px" |  
Line 40: Line 38:
 
=== Enabled ===
 
=== Enabled ===
  
Enable or Disable the use of Response Profiles.
+
Enable or Disable response&nbsp;types&nbsp;section.
 
 
==== TRUE ====
 
 
 
Enable this section
 
 
 
==== FALSE ====
 
  
Disable this section
+
*'''TRUE&nbsp;''': Enable response&nbsp;types section.
 +
*'''FALSE&nbsp;''': Disable response&nbsp;types section.
  
 
| style="width: 307px" | &nbsp;
 
| style="width: 307px" | &nbsp;
Line 54: Line 47:
 
| style="width: 957px" |  
 
| style="width: 957px" |  
 
[[File:Response typeSlide1 (2).PNG|border|center|Response typeSlide1 (2).PNG|link=]]
 
[[File:Response typeSlide1 (2).PNG|border|center|Response typeSlide1 (2).PNG|link=]]
 
&nbsp;
 
  
 
&nbsp; [[File:Response typeSlide1 (3).PNG|border|center|Response typeSlide1 (3).PNG|link=]]
 
&nbsp; [[File:Response typeSlide1 (3).PNG|border|center|Response typeSlide1 (3).PNG|link=]]
Line 62: Line 53:
 
|-
 
|-
 
| style="width: 957px" |  
 
| style="width: 957px" |  
== Response Profiler ==
+
== Response Types ==
  
 
The following rules are tested for each connection.
 
The following rules are tested for each connection.
Line 68: Line 59:
 
The testing is done in top-down order.
 
The testing is done in top-down order.
  
The first entry that matches the Response Profile of a connection, is applied to it.
+
The first entry that matches the Response Profile of a connection, will be applied to it.
  
 
| style="width: 307px" | &nbsp;
 
| style="width: 307px" | &nbsp;
Line 80: Line 71:
 
Enable or Disable this entry.
 
Enable or Disable this entry.
  
==== TRUE ====
+
*'''TRUE&nbsp;''': Enable this entry.
 
+
*'''FALSE&nbsp;''': Disable this entry.
Enable this entry
 
 
 
==== FALSE ====
 
 
 
Disable this entry
 
  
 
=== Comment ===
 
=== Comment ===
Line 100: Line 86:
 
Enable entry tracing, is useful if you wish to validate, its application.
 
Enable entry tracing, is useful if you wish to validate, its application.
  
==== TRUE ====
+
*'''TRUE&nbsp;''': Select this option to enable profile tracing.
 
+
*'''FALSE&nbsp;''': Select this option to disable profile tracing.
Enable tracing of this entry
 
 
 
==== FALSE ====
 
 
 
Disable tracing of this entry
 
  
=== Response Profiles ===
+
=== Response Types ===
  
 
Specify the list of Response Profile(s)for which this entry should be applicable.
 
Specify the list of Response Profile(s)for which this entry should be applicable.
Line 118: Line 99:
 
To avoid application to a connection for specific Response Profile(s), use negation (!Response Profile).
 
To avoid application to a connection for specific Response Profile(s), use negation (!Response Profile).
  
=== Mime type ===
+
=== Content type ===
  
 
Specify the MIME-type for which this entry should be applicable.
 
Specify the MIME-type for which this entry should be applicable.
Line 128: Line 109:
 
This entry applies to the regular expression matching the MIME-type.
 
This entry applies to the regular expression matching the MIME-type.
  
Example: text/html, ^image/, ^application/, application/x-shockwave-flash.
+
'''Example:''' text/html, ^image/, ^application/, application/x-shockwave-flash.
  
 
If this entry should be applied to all responses, irrespective of MIME-type, leave it blank.
 
If this entry should be applied to all responses, irrespective of MIME-type, leave it blank.
Line 142: Line 123:
 
=== Transfer Encoding Chunk ===
 
=== Transfer Encoding Chunk ===
  
This option is to control how the transfer encoding chunk header should be handled. Example: Transfer-Encoding: chunked
+
This option is to control how the transfer encoding chunk header should be handled.<br/> '''Example:''' Transfer-Encoding: chunked
  
==== Any ====
+
==== ANY ====
  
 
Select this if transfer encoding chunked does not matter in response header.
 
Select this if transfer encoding chunked does not matter in response header.
  
==== False ====
+
==== NO ====
  
 
Select this if you don't want to apply profile if transfer encoding chunked present in response header.
 
Select this if you don't want to apply profile if transfer encoding chunked present in response header.
  
==== True ====
+
==== YES ====
  
 
Select this if you want to apply profile if transfer encoding chunked present in response header.
 
Select this if you want to apply profile if transfer encoding chunked present in response header.
  
=== Multipart_byterange ===
+
=== multipart_byterange ===
  
This option is to control how the multi part/ byte ranges header should be handled. Example: Content-type: multipart/x-byteranges; boundary=THIS_STRING_SEPARATES --THIS_STRING_SEPARATES Content-type: application/x-pdf Content-range: bytes 500-999/8000 ...the first range... --THIS_STRING_SEPARATES Content-type: application/x-pdf Content-range: bytes 7000-7999/8000 ...the second range... --THIS_STRING_SEPARATES--
+
This option is to control how the multi part/ byte ranges header should be handled.<br/> '''Example:''' Content-type: multipart/x-byteranges; boundary=THIS_STRING_SEPARATES --THIS_STRING_SEPARATES<br/> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Content-type: application/x-pdf Content-range: bytes 500-999/8000 ...the first range... --THIS_STRING_SEPARATES<br/> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Content-type: application/x-pdf Content-range: bytes 7000-7999/8000 ...the second range... --THIS_STRING_SEPARATES--
  
==== Any ====
+
==== ANY ====
  
Select this if multipart byte range does not matter in response header.
+
Select this if multipart/ byterange does not matter in response header.
  
==== False ====
+
==== NO ====
  
Select this if you don't want to apply profile if multipart byte ranges present in response header.
+
Select this if you don't want to apply profile if multipart/ byteranges present in response header.
  
==== True ====
+
==== YES ====
  
Select this if you want to apply profile if multipart byte ranges present in response header.
+
Select this if you want to apply profile if multipart/ byteranges present in response header.
  
 
=== Minimum Content Size ===
 
=== Minimum Content Size ===
Line 186: Line 167:
 
If left blank, applies to all response patterns.
 
If left blank, applies to all response patterns.
  
=== Added Response Profiles ===
+
=== Added Response Types ===
  
 
Specify the list of Response Profiles, to append to the connection’s existing Response Profiles, if the all the applicability test rules match.
 
Specify the list of Response Profiles, to append to the connection’s existing Response Profiles, if the all the applicability test rules match.
Line 196: Line 177:
 
When defining a new Response Profile, use terms that uniquely represent your needs.
 
When defining a new Response Profile, use terms that uniquely represent your needs.
  
=== Removed Response Profiles ===
+
=== Removed Response Types ===
  
 
Specify the list of Response Profile(s), to remove the connection’s existing Profiles, if the all the applicability test rules match.
 
Specify the list of Response Profile(s), to remove the connection’s existing Profiles, if the all the applicability test rules match.

Revision as of 18:00, 19 October 2018

Overview

Use Response profiles to manage profiling based on the responses received from the webserver.
You can manage Profiling based on the following parameters present in the responses received from the webserver.

  • Mime
  • File
  • Content-Length
  • Response header pattern, etc.,

Enabling Response Profiler section on SafeSquid User Interface

Access SafeSquid interface

Go to configure page

AllowsitescategorySlide1 (2).PNG
 

Go to custom settings

 
Time ProfileSlide1 (1).PNG
 
Response typeSlide1 (1).PNG
 

Global

Enabled

Enable or Disable response types section.

  • TRUE : Enable response types section.
  • FALSE : Disable response types section.
 
Response typeSlide1 (2).PNG
 
Response typeSlide1 (3).PNG
 

Response Types

The following rules are tested for each connection.

The testing is done in top-down order.

The first entry that matches the Response Profile of a connection, will be applied to it.

 
Respons-policies.jpg
 

Enabled

Enable or Disable this entry.

  • TRUE : Enable this entry.
  • FALSE : Disable this entry.

Comment

For documentation, and future references, explain the relevance of this entry with your policies.

Trace Entry

Enable or Disable Tracing of this entry

Select “Yes” to debug the application of entry using SafeSquid logs.

Enable entry tracing, is useful if you wish to validate, its application.

  • TRUE : Select this option to enable profile tracing.
  • FALSE : Select this option to disable profile tracing.

Response Types

Specify the list of Response Profile(s)for which this entry should be applicable.

Leave it Blank, to ignore this applicability test.

If one or more Response Profiles are specified, this entry will be applicable only after, response has been received from the web server.

To avoid application to a connection for specific Response Profile(s), use negation (!Response Profile).

Content type

Specify the MIME-type for which this entry should be applicable.

MIME-type is a way of identifying files on the Internet according to their nature and format.

Here, MIME-type indicates the response-body received from the server.

This entry applies to the regular expression matching the MIME-type.

Example: text/html, ^image/, ^application/, application/x-shockwave-flash.

If this entry should be applied to all responses, irrespective of MIME-type, leave it blank.

File Extension

Specify the file extensions for which this entry should be applicable.

This entry applies to the regular expression matching the extension of file(s) obtained in response body.

Leave it blank to apply all the requests, irrespective of file extension.

Transfer Encoding Chunk

This option is to control how the transfer encoding chunk header should be handled.
Example: Transfer-Encoding: chunked

ANY

Select this if transfer encoding chunked does not matter in response header.

NO

Select this if you don't want to apply profile if transfer encoding chunked present in response header.

YES

Select this if you want to apply profile if transfer encoding chunked present in response header.

multipart_byterange

This option is to control how the multi part/ byte ranges header should be handled.
Example: Content-type: multipart/x-byteranges; boundary=THIS_STRING_SEPARATES --THIS_STRING_SEPARATES
                 Content-type: application/x-pdf Content-range: bytes 500-999/8000 ...the first range... --THIS_STRING_SEPARATES
                 Content-type: application/x-pdf Content-range: bytes 7000-7999/8000 ...the second range... --THIS_STRING_SEPARATES--

ANY

Select this if multipart/ byterange does not matter in response header.

NO

Select this if you don't want to apply profile if multipart/ byteranges present in response header.

YES

Select this if you want to apply profile if multipart/ byteranges present in response header.

Minimum Content Size

Specify the minimum content size of the response body for which this entry is applicable.

Maximum Content Size

Specify the maximum content size of the response body for which this entry is applicable.

Response Header Pattern

Specify the regular expression matching the response header pattern for which this entry is applicable.

If left blank, applies to all response patterns.

Added Response Types

Specify the list of Response Profiles, to append to the connection’s existing Response Profiles, if the all the applicability test rules match.

Subsequent applicable Entry may further modify the connection’s Response Profiles.

Define a new Response Profile(s), or Select previously defined Response Profile(s)from the drop-down menu to apply to the connection, if it matches this entry.

When defining a new Response Profile, use terms that uniquely represent your needs.

Removed Response Types

Specify the list of Response Profile(s), to remove the connection’s existing Profiles, if the all the applicability test rules match.

Subsequent applicable Entry may further modify the connection’s Response Profiles.

Select previously defined Response Profile(s)from the drop-down menu to apply to the connection, if it matches this entry.