Changes

===Proxy Pass===

==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

  db domains delete proxypassdomain.com

  db domains delete proxypassdomain.com

  signal-event domain-delete proxypassdomain.com

  signal-event domain-delete proxypassdomain.com

{{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]]}}

http://forums.contribs.org/index.php?topic=46975.0

http://forums.contribs.org/index.php?topic=46975.0

From this forum post by Charlie Brady http://forums.contribs.org/index.php?action=post;quote=245408;topic=49181.0;last_msg=245408 is information about https access & expected behaviour re certificates

From this forum post by Charlie Brady http://forums.contribs.org/index.php/topic,49181.msg245408.html#msg245408 is information about https access & expected behaviour re certificates

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

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.

http://httpd.apache.org/docs/2.0/mod/mod_headers.html

http://httpd.apache.org/docs/2.0/mod/mod_headers.html

*User feedback & additional information re above method:

*User feedback & additional information re above method:

To achieve this, Apache must resolve everything to iBays, except the one virtual host and it's /owa directories.

To achieve this, Apache must resolve everything to iBays, except the one virtual host and it's /owa directories.

1. Enable SSLProxy:

1. Enable SSLProxy:

  # End of Exchange settings

  # End of Exchange settings

  </VirtualHost>

  </VirtualHost>

where iis.private.local is the private instance of IIS. and remote.domainA.com is a publically addressable domain that resolves to the public side of the SME server. To be sure this works, you must be able to resolve iis.private.local from the sme server (add a hostname record with correct internal IP address). Ensure the Integrated Authentication is disabled for OWA (leave basic auth on).

where iis.private.local is the private instance of IIS. and remote.domainA.com is a publically addressable domain that resolves to the public side of the SME server. To be sure this works, you must be able to resolve iis.private.local from the sme server (add a hostname record with correct internal IP address). Ensure the Integrated Authentication is disabled for OWA (leave basic auth on).

Google

Google