Line 1: |
Line 1: |
− | ===Proxy Pass===
| + | {{usefulnote}} |
| + | ==Proxy Pass== |
| | | |
− | ====ProxyPass a domain====
| + | ===ProxyPass a domain=== |
| | | |
| This section covers ProxyPass directives in the "domains" database | | This section covers ProxyPass directives in the "domains" database |
Line 19: |
Line 20: |
| db domains delete proxypassdomain.com | | db domains delete proxypassdomain.com |
| signal-event domain-delete proxypassdomain.com | | signal-event domain-delete proxypassdomain.com |
| + | |
| + | Note that using the settings above 'TemplatePath' is set to 'ProxyPassVirtualHosts' which will read templates in: |
| + | |
| + | /etc/e-smith/templates/etc/httpd/conf/httpd.conf/ProxyPassVirtualHosts |
| + | |
| + | It is perfectly possible to use your own templates for more specialised settings: |
| + | |
| + | cp -R /etc/e-smith/templates/etc/httpd/conf/httpd.conf/ProxyPassVirtualHosts /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/MyProxyPassHost |
| + | |
| + | Now you can edit the templates in 'MyProxyPassHost' and use your own advanced settings as you require. |
| + | |
| + | db domains setprop proxypassdomain.com TemplatePath MyProxyPassHost |
| | | |
| {{Note box|msg=If you have added the internal or external server's domain name as a virtual domain on the SME Server, you must remove it prior to issuing these commands. The server-manager domains panel will show the proxy pass entry but you will not be able to edit it, see [[bugzilla:1612]]}} | | {{Note box|msg=If you have added the internal or external server's domain name as a virtual domain on the SME Server, you must remove it prior to issuing these commands. The server-manager domains panel will show the proxy pass entry but you will not be able to edit it, see [[bugzilla:1612]]}} |
Line 34: |
Line 47: |
| What happens is that the browser connects to the SME server, then negotiates SSL (verifies the certificate and starts encrypting the connection), then sends the request (hostname + URL). Apache in the SME server then proxies the connection (creates the connection to the internal webserver, passes the request, passes back the response). There's no way that the internal server's certificate can be presented to the browser and used to enable encryption. | | What happens is that the browser connects to the SME server, then negotiates SSL (verifies the certificate and starts encrypting the connection), then sends the request (hostname + URL). Apache in the SME server then proxies the connection (creates the connection to the internal webserver, passes the request, passes back the response). There's no way that the internal server's certificate can be presented to the browser and used to enable encryption. |
| | | |
− | ====ProxyPass a alias/directory/location====
| + | ===ProxyPass a alias/directory/location=== |
| | | |
| This section covers the db settings in the "accounts" database that generate ProxyPass directives in httpd.conf | | This section covers the db settings in the "accounts" database that generate ProxyPass directives in httpd.conf |
Line 65: |
Line 78: |
| http://forums.contribs.org/index.php/topic,40075.0.html | | http://forums.contribs.org/index.php/topic,40075.0.html |
| | | |
− | ====ProxyPass for Exchange Outlook Web Access====
| + | ===ProxyPass for Exchange Outlook Web Access=== |
| | | |
| Users wishing to implement this setup are strongly advised to read in full this forum thread http://forums.contribs.org/index.php/topic,40075.0.html from which the following information was obtained. | | Users wishing to implement this setup are strongly advised to read in full this forum thread http://forums.contribs.org/index.php/topic,40075.0.html from which the following information was obtained. |
Line 244: |
Line 257: |
| Google | | Google |
| | | |
− | ====DNS Forwarding====
| + | ==DNS Forwarding== |
| | | |
| The dnscache service can be configured to forward all queries for a specific domain to an alternate server, or to block DNS for a domain by configuring forwarding to 'localhost', without affecting any other services or configuration files. See [[Bugzilla:6848]] | | The dnscache service can be configured to forward all queries for a specific domain to an alternate server, or to block DNS for a domain by configuring forwarding to 'localhost', without affecting any other services or configuration files. See [[Bugzilla:6848]] |
Line 255: |
Line 268: |
| To block lookups for <domainname>: | | To block lookups for <domainname>: |
| db domains set <domainname> domain-remote localhost | | db domains set <domainname> domain-remote localhost |
| + | [[Category: Howto]] |