624
edits
Changes
Jump to navigation
Jump to search
mLine 30:
Line 30: − +
SME Server:Documentation:ProxyPass (view source)
Revision as of 03:36, 23 October 2012
, 03:36, 23 October 2012corrected URL re certificate behaviour link
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.