BES - Modules - Gateway Module - Revision history

Jimg: /* Using Squid on OS/X */

2011-10-10T22:10:48Z

Using Squid on OS/X

← Older revision		Revision as of 22:10, 10 October 2011
Line 72:		Line 72:
	Gateway.ProxyHost=localhost		Gateway.ProxyHost=localhost
	Gateway.ProxyPort=3218		Gateway.ProxyPort=3218
	Gateway.NoProxy=http://localhost.*		<nowiki>Gateway.NoProxy=http://localhost.*</nowiki>

	assuming you're running both Squid and Hyrax on the same host.		assuming you're running both Squid and Hyrax on the same host.

Jimg: /* Using Squid on OS/X */

2011-10-10T22:10:23Z

Using Squid on OS/X

← Older revision		Revision as of 22:10, 10 October 2011
Line 72:		Line 72:
	Gateway.ProxyHost=localhost		Gateway.ProxyHost=localhost
	Gateway.ProxyPort=3218		Gateway.ProxyPort=3218
			Gateway.NoProxy=http://localhost.*

	assuming you're running both Squid and Hyrax on the same host.		assuming you're running both Squid and Hyrax on the same host.

Jimg: /* Network proxies and Performance optimizations */

2011-10-10T22:09:44Z

Network proxies and Performance optimizations

← Older revision		Revision as of 22:09, 10 October 2011
Line 21:		Line 21:

	=== Network proxies and Performance optimizations ===		=== Network proxies and Performance optimizations ===
	There are four parameters that are used to configure a proxy server. Nominally this is used as a cache, so that files do not have to be repeatedly fetched from the remote service and that's why we consider this a 'performance' feature. We have tested the hander with Squid because it is widely used on both linux and OS/X and because in addition to it's proxy capabilities, it is often used as a cache. This can also be used to navigate firewalls.		There are four parameters that are used to configure a proxy server that the gateway will use. Nominally this is used as a cache, so that files do not have to be repeatedly fetched from the remote service and that's why we consider this a 'performance' feature. We have tested the hander with Squid because it is widely used on both linux and OS/X and because in addition to it's proxy capabilities, it is often used as a cache. This can also be used to navigate firewalls.

	;Gateway.ProxyProtocol: Which protocol(s) does this proxy support. Nominally this should be ''http''.		;Gateway.ProxyProtocol: Which protocol(s) does this proxy support. Nominally this should be ''http''.

Jimg: /* Network proxies and Performance optimizations */

2011-10-10T21:07:46Z

Network proxies and Performance optimizations

← Older revision		Revision as of 21:07, 10 October 2011
Line 26:		Line 26:
	;Gateway.ProxyHost: On what host does the proxy server operate? Often you want to use ''localgost'' for this.		;Gateway.ProxyHost: On what host does the proxy server operate? Often you want to use ''localgost'' for this.
	;Gateway.ProxyPort: What port does the proxy listen on? Squid defaults to ''3218''; some documentation for web accelerators		;Gateway.ProxyPort: What port does the proxy listen on? Squid defaults to ''3218''; some documentation for web accelerators
	;Gateway.NoProxy: Provide a regular expression that describes URLs that should ''not'' be sent to the proxy. This is particularly useful for running the gateway on the hosts that stage the service accessed via the gateway. In this cases, a proxy/cache like squid may not process 'localhost' URLs unless its configuration is tweaked quite a bit (and there may be no performance advantage to having the proxy/cache store extra copies of the files given that they are on the host already.		;Gateway.NoProxy: Provide a regular expression that describes URLs that should ''not'' be sent to the proxy. This is particularly useful for running the gateway on the hosts that stage the service accessed via the gateway. In this cases, a proxy/cache like squid may not process 'localhost' URLs unless its configuration is tweaked quite a bit (and there may be no performance advantage to having the proxy/cache store extra copies of the files given that they are on the host already). This parameter was added in version 1.1.0.

	Gateway.ProxyProtocol=		Gateway.ProxyProtocol=
	Gateway.ProxyHost=		Gateway.ProxyHost=
	Gateway.ProxyPort=		Gateway.ProxyPort=
			Gateway.NoProxy=

	====Using Squid====		====Using Squid====

Jimg: /* Network proxies and Performance optimizations */

2011-10-10T21:06:12Z

Network proxies and Performance optimizations

← Older revision		Revision as of 21:06, 10 October 2011
Line 21:		Line 21:

	=== Network proxies and Performance optimizations ===		=== Network proxies and Performance optimizations ===
	;Gateway.ProxyHost		There are four parameters that are used to configure a proxy server. Nominally this is used as a cache, so that files do not have to be repeatedly fetched from the remote service and that's why we consider this a 'performance' feature. We have tested the hander with Squid because it is widely used on both linux and OS/X and because in addition to it's proxy capabilities, it is often used as a cache. This can also be used to navigate firewalls.
	;Gateway.ProxyPort: ~~provide a way~~ to ~~define~~ a ~~proxy server~~ that ~~must~~ be ~~used~~ to ~~make~~ the ~~remote request~~. This ~~can~~ be ~~used~~ to ~~increase performance as well as navigate firewalls~~.
			;Gateway.ProxyProtocol: Which protocol(s) does this proxy support. Nominally this should be ''http''.
			;Gateway.ProxyHost: On what host does the proxy server operate? Often you want to use ''localgost'' for this.
			;Gateway.ProxyPort: What port does the proxy listen on? Squid defaults to ''3218''; some documentation for web accelerators
			;Gateway.NoProxy: Provide a regular expression that describes URLs that should ''not'' be sent to the proxy. This is particularly useful for running the gateway on the hosts that stage the service accessed via the gateway. In this cases, a proxy/cache like squid may not process 'localhost' URLs unless its configuration is tweaked quite a bit (and there may be no performance advantage to having the proxy/cache store extra copies of the files given that they are on the host already.

	Gateway.ProxyProtocol=		Gateway.ProxyProtocol=

Jimg at 21:35, 21 April 2011

2011-04-21T21:35:51Z

← Older revision		Revision as of 21:35, 21 April 2011
Line 83:		Line 83:
	# Edit the line, replacing "0 0% 0" with "1440 20% 10080"; and		# Edit the line, replacing "0 0% 0" with "1440 20% 10080"; and
	# 'Save' and then 'Stop Squid' and 'Start Squid' (note the helpful status messages in the 'Start/Stop' window).[[Image:Squid 1.png\|200px]][[Image:Squid 2.png\|200px]][[Image:Squid 3.png\|200px]]		# 'Save' and then 'Stop Squid' and 'Start Squid' (note the helpful status messages in the 'Start/Stop' window).[[Image:Squid 1.png\|200px]][[Image:Squid 2.png\|200px]][[Image:Squid 3.png\|200px]]

			==Known Problems==

			For version 1.0.1 of the gateway, we know about the following problems:

			# Squid does not cache requests to localhost, but our use of the proxy server does not by-pass requests to localhost. Thus, using the gateway to access data from a service running on localhost will fail when using squid since the gateway will route the request to the proxy (i.e., squid) where it will generate an error.
			# Not using a caching proxy server will result in poor performance.

Jimg: /* Using Squid */

2011-04-19T19:38:47Z

Using Squid

← Older revision		Revision as of 19:38, 19 April 2011
Line 30:		Line 30:
	====Using Squid====		====Using Squid====
	Squid makes a great cache for the gateway. In our testing we have used Squid only for services running on port 80.		Squid makes a great cache for the gateway. In our testing we have used Squid only for services running on port 80.

			Squid is a powerful tool and it is worth looking at its [http://www.squid-cache.org/ web page].

	====Squid and Dynamic Content====		====Squid and Dynamic Content====

Jimg: /* Squid, OS/X and Caching Dynamic Content */

2011-04-19T19:31:18Z

Squid, OS/X and Caching Dynamic Content

← Older revision		Revision as of 19:31, 19 April 2011
Line 77:		Line 77:

	====Squid, OS/X and Caching Dynamic Content====		====Squid, OS/X and Caching Dynamic Content====
	By default SquidMan does not cache dynamic content that lacks cache control headers in the response. To hack the squid.conf file and make the change in the ''~~request_pattern~~'' described above do the following:		By default SquidMan does not cache dynamic content that lacks cache control headers in the response. To hack the squid.conf file and make the change in the ''refresh_pattern'' described above do the following:
	# Under Preferences... choose the 'Template' tab and scroll to the bottom of the text;[[Image:Edit the squid.conf file.png\|200px]]		# Under Preferences... choose the 'Template' tab and scroll to the bottom of the text;[[Image:Edit the squid.conf file.png\|200px]]
	# Edit the line, replacing "0 0% 0" with "1440 20% 10080"; and		# Edit the line, replacing "0 0% 0" with "1440 20% 10080"; and
	# 'Save' and then 'Stop Squid' and 'Start Squid' (note the helpful status messages in the 'Start/Stop' window).[[Image:Squid 1.png\|200px]][[Image:Squid 2.png\|200px]][[Image:Squid 3.png\|200px]]		# 'Save' and then 'Stop Squid' and 'Start Squid' (note the helpful status messages in the 'Start/Stop' window).[[Image:Squid 1.png\|200px]][[Image:Squid 2.png\|200px]][[Image:Squid 3.png\|200px]]

Jimg: /* Using Squid on OS/X */

2011-04-19T17:35:25Z

Using Squid on OS/X

← Older revision		Revision as of 17:35, 19 April 2011
Line 75:		Line 75:
	fetches the data, will say ''DIRECT/<ip number>'' while cache hits		fetches the data, will say ''DIRECT/<ip number>'' while cache hits
	will be labeled ''NONE/-''.		will be labeled ''NONE/-''.

			====Squid, OS/X and Caching Dynamic Content====
			By default SquidMan does not cache dynamic content that lacks cache control headers in the response. To hack the squid.conf file and make the change in the ''request_pattern'' described above do the following:
			# Under Preferences... choose the 'Template' tab and scroll to the bottom of the text;[[Image:Edit the squid.conf file.png\|200px]]
			# Edit the line, replacing "0 0% 0" with "1440 20% 10080"; and
			# 'Save' and then 'Stop Squid' and 'Start Squid' (note the helpful status messages in the 'Start/Stop' window).[[Image:Squid 1.png\|200px]][[Image:Squid 2.png\|200px]][[Image:Squid 3.png\|200px]]

Jimg: /* Using Squid */

2011-04-19T17:18:03Z

Using Squid

@@ Line 29: / Line 29: @@
 ====Using Squid====
-Squid makes a great cache for the gateway. In our
+Squid makes a great cache for the gateway. In our testing we have used Squid only for services running on port 80.
-testing we have  used Squid only for services running on port 80.
 ====Using Squid on OS/X====