Re: Having modssl run on different ports, is this even possible?
Michael Pacey <[email protected]>
| Newsgroups | gmane.comp.apache.mod-ssl.user |
|---|---|
| Message-ID | <1160609022.5501.14.camel@gandalf> |
On Wed, 2006-10-11 at 14:31 -0700, Yvo van Doorn wrote: > I am running Apache2 with the included mod_ssl module, I figure this a > good place to start, but if it belongs on the apache httpd mailing > list you can bluntly tell me. > > The servers I administer run in an environment that is pretty painful, > but common i hear. Another team at corporate headquarters administer > the firewall and what they are planning to do is as follows. I have no > control over the firewall what so ever. > > Any port 80 (http) request sent to the firewall for domain > www.example.com will be then rerouted to an internal IP, such as > 172.16.15.102 (behind the firewall), on port 8000. Thus I have apache > listening on port 8000. > > Any port 443 (https) request sent to the firewall for domain > www.example.com will be then rerouted to to an internal IP, such as > 172.16.15.102 (behind the firewall), on port 9000. I want to have > mod_ssl listening on port 9000, is this possible? > > Should a virtualhost entry just work such <VirtualHost > 172.16.15.102:9000> and have the usual items such as SSLEngine, > SSLCertificateFile, SSLCertificateKeyFile, etc? Yes that should work. Make sure you have your ports in the Listen directive. ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [email protected] Automated List Manager [email protected]