Difference between revisions of "Response Types"

Revision as of 15:43, 29 April 2017 (view source) Paulie1 (talk | contribs) (Created page with " Under Construction")		Revision as of 20:03, 2 May 2017 (view source) Samidha12 (talk | contribs) Newer edit →
Line 1:		Line 1:
−	Under Construction	+	Use Response profiles to manage profiling based on the responses received from the webserver.
		+
		+	Profiling can be managed based on the following parameters present in the responses received from the webserver.
		+
		+	*Mime
		+	*File
		+	*Content-Length
		+	*Response header pattern, etc.,
		+
		+	== Global ==
		+
		+	== [[File:Respons-global.jpg|link=]] ==
		+
		+	=== Enabled ===
		+
		+	Enable or Disable the use of Response Profiles.
		+
		+	==== TRUE ====
		+
		+	Enable this section
		+
		+	==== FALSE ====
		+
		+	Disable this section
		+
		+	== Response Profiler ==
		+
		+	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, is applied to it.
		+
		+	[[File:Respons-policies.jpg|link=]]
		+
		+	=== Enabled ===
		+
		+	Enable or Disable this entry.
		+
		+	==== TRUE ====
		+
		+	Enable this entry
		+
		+	==== FALSE ====
		+
		+	Disable this entry
		+
		+	=== Comment ===
		+
		+	For documentation, and future references, explainthe 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 ====
		+
		+	Enable tracing of this entry
		+
		+	==== FALSE ====
		+
		+	Disable tracing of this entry
		+
		+	=== ResponseProfiles ===
		+
		+	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).
		+
		+	=== Mimetype ===
		+
		+	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.
		+
		+	=== FileExtension ===
		+
		+	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.
		+
		+	==== False ====
		+
		+	Select this if you don't want to apply profile if transfer encoding chunked present in response header.
		+
		+	==== True ====
		+
		+	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.
		+
		+	==== False ====
		+
		+	Select this if you don't want to apply profile if multipart byteranges present in response header.
		+
		+	==== True ====
		+
		+	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 responsepatterns.
		+
		+	=== Added Response Profiles ===
		+
		+	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 Profiles ===
		+
		+	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.

---

Revision as of 20:03, 2 May 2017

Use Response profiles to manage profiling based on the responses received from the webserver.

Profiling can be managed based on the following parameters present in the responses received from the webserver.

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

Global

Enabled

Enable or Disable the use of Response Profiles.

TRUE

Enable this section

FALSE

Disable this section

Response Profiler

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, is applied to it.

Enabled

Enable or Disable this entry.

TRUE

Enable this entry

FALSE

Disable this entry

Comment

For documentation, and future references, explainthe 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

Enable tracing of this entry

FALSE

Disable tracing of this entry

ResponseProfiles

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).

Mimetype

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.

FileExtension

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.

False

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

True

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.

False

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

True

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 responsepatterns.

Added Response Profiles

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 Profiles

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.