<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Setup virtual host with apache and ssl in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/setup-virtual-host-with-apache-and-ssl/m-p/4984916#M782945</link>
    <description>I am attempting to establish a number of virtual web hosts using ssl and apache.  I can't seem to get ssl to work on any but the "main" host.&lt;BR /&gt;I am using: &lt;BR /&gt;HP-UX  11i v1, and the HP apache depot for version 2.0.55.  The system has two network cards with one of them with two ip addresses 139.x.y.z1 and 139.x.y.z2&lt;BR /&gt;&lt;BR /&gt;I can start the web server in ssl mode using ../bin/apachectl startssl.&lt;BR /&gt;&lt;BR /&gt;All but the main web can only be contacted with a url like  &lt;A href="http://139.x.y.z1:443." target="_blank"&gt;http://139.x.y.z1:443.&lt;/A&gt;  Using a url like https:/139.x.y.z1 gives an empty page and no apparent error message.  The main web service can be contacted through the other network card with something like &lt;A href="https://139.x.y1.z3." target="_blank"&gt;https://139.x.y1.z3.&lt;/A&gt;  I was also trying to trap any other access and not give any access.&lt;BR /&gt;&lt;BR /&gt;I have included what I think are the relevant parts of the httpd.conf file.  Any assistance greatly appreciated. &lt;BR /&gt;&lt;BR /&gt;#----------------------&lt;BR /&gt;# httpd.conf bits&lt;BR /&gt;Listen 139.x.y.z1:443&lt;BR /&gt;Listen 139.x.y.z2:443&lt;BR /&gt;# .....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;#------------------&lt;BR /&gt;#&lt;BR /&gt;&lt;VIRTUALHOST&gt;&lt;BR /&gt;  DocumentRoot  /opt/hpws/apache/htdocs&lt;BR /&gt;  ErrorLog logs/default_error_log&lt;BR /&gt;  TransferLog logs/default_access_log&lt;BR /&gt;  &lt;DIRECTORY&gt;&lt;BR /&gt;     Options    none&lt;BR /&gt;     Order deny,allow&lt;BR /&gt;     Deny from all&lt;BR /&gt;   &lt;/DIRECTORY&gt;&lt;BR /&gt;&lt;/VIRTUALHOST&gt;&lt;BR /&gt;#---&lt;BR /&gt;&lt;VIRTUALHOST 443=""&gt; &lt;BR /&gt;  DocumentRoot  /opt/hpws/apache/htdocs&lt;BR /&gt;  ServerName 139.x.y.z1     &lt;BR /&gt;  ServerAlias   hp4&lt;BR /&gt;  ErrorLog logs/hp4_error_log&lt;BR /&gt;  TransferLog logs/hp4_access_log&lt;BR /&gt;&lt;/VIRTUALHOST&gt;&lt;BR /&gt;#---&lt;BR /&gt;&lt;VIRTUALHOST 443=""&gt;     &lt;BR /&gt;#  ServerAdmin  root@hp4.usq.edu.au&lt;BR /&gt;  DocumentRoot  /opt/hpws/apache/hpweb4&lt;BR /&gt;  ServerName  139.x.y.z2        &lt;BR /&gt;  ServerAlias hpweb4&lt;BR /&gt;  ErrorLog  logs/hpweb4_error_log&lt;BR /&gt;  TransferLog   logs/hpweb4_access_log&lt;BR /&gt;  &lt;DIRECTORY&gt;&lt;BR /&gt;     Options Indexes FollowSymLinks&lt;BR /&gt;     Order allow,deny&lt;BR /&gt;     Allow from all&lt;BR /&gt;  &lt;/DIRECTORY&gt;&lt;BR /&gt;&lt;/VIRTUALHOST&gt;&lt;BR /&gt;#------------------</description>
    <pubDate>Mon, 12 Jun 2006 22:41:10 GMT</pubDate>
    <dc:creator>David Woodroffe</dc:creator>
    <dc:date>2006-06-12T22:41:10Z</dc:date>
    <item>
      <title>Setup virtual host with apache and ssl</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/setup-virtual-host-with-apache-and-ssl/m-p/4984916#M782945</link>
      <description>I am attempting to establish a number of virtual web hosts using ssl and apache.  I can't seem to get ssl to work on any but the "main" host.&lt;BR /&gt;I am using: &lt;BR /&gt;HP-UX  11i v1, and the HP apache depot for version 2.0.55.  The system has two network cards with one of them with two ip addresses 139.x.y.z1 and 139.x.y.z2&lt;BR /&gt;&lt;BR /&gt;I can start the web server in ssl mode using ../bin/apachectl startssl.&lt;BR /&gt;&lt;BR /&gt;All but the main web can only be contacted with a url like  &lt;A href="http://139.x.y.z1:443." target="_blank"&gt;http://139.x.y.z1:443.&lt;/A&gt;  Using a url like https:/139.x.y.z1 gives an empty page and no apparent error message.  The main web service can be contacted through the other network card with something like &lt;A href="https://139.x.y1.z3." target="_blank"&gt;https://139.x.y1.z3.&lt;/A&gt;  I was also trying to trap any other access and not give any access.&lt;BR /&gt;&lt;BR /&gt;I have included what I think are the relevant parts of the httpd.conf file.  Any assistance greatly appreciated. &lt;BR /&gt;&lt;BR /&gt;#----------------------&lt;BR /&gt;# httpd.conf bits&lt;BR /&gt;Listen 139.x.y.z1:443&lt;BR /&gt;Listen 139.x.y.z2:443&lt;BR /&gt;# .....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;#------------------&lt;BR /&gt;#&lt;BR /&gt;&lt;VIRTUALHOST&gt;&lt;BR /&gt;  DocumentRoot  /opt/hpws/apache/htdocs&lt;BR /&gt;  ErrorLog logs/default_error_log&lt;BR /&gt;  TransferLog logs/default_access_log&lt;BR /&gt;  &lt;DIRECTORY&gt;&lt;BR /&gt;     Options    none&lt;BR /&gt;     Order deny,allow&lt;BR /&gt;     Deny from all&lt;BR /&gt;   &lt;/DIRECTORY&gt;&lt;BR /&gt;&lt;/VIRTUALHOST&gt;&lt;BR /&gt;#---&lt;BR /&gt;&lt;VIRTUALHOST 443=""&gt; &lt;BR /&gt;  DocumentRoot  /opt/hpws/apache/htdocs&lt;BR /&gt;  ServerName 139.x.y.z1     &lt;BR /&gt;  ServerAlias   hp4&lt;BR /&gt;  ErrorLog logs/hp4_error_log&lt;BR /&gt;  TransferLog logs/hp4_access_log&lt;BR /&gt;&lt;/VIRTUALHOST&gt;&lt;BR /&gt;#---&lt;BR /&gt;&lt;VIRTUALHOST 443=""&gt;     &lt;BR /&gt;#  ServerAdmin  root@hp4.usq.edu.au&lt;BR /&gt;  DocumentRoot  /opt/hpws/apache/hpweb4&lt;BR /&gt;  ServerName  139.x.y.z2        &lt;BR /&gt;  ServerAlias hpweb4&lt;BR /&gt;  ErrorLog  logs/hpweb4_error_log&lt;BR /&gt;  TransferLog   logs/hpweb4_access_log&lt;BR /&gt;  &lt;DIRECTORY&gt;&lt;BR /&gt;     Options Indexes FollowSymLinks&lt;BR /&gt;     Order allow,deny&lt;BR /&gt;     Allow from all&lt;BR /&gt;  &lt;/DIRECTORY&gt;&lt;BR /&gt;&lt;/VIRTUALHOST&gt;&lt;BR /&gt;#------------------</description>
      <pubDate>Mon, 12 Jun 2006 22:41:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/setup-virtual-host-with-apache-and-ssl/m-p/4984916#M782945</guid>
      <dc:creator>David Woodroffe</dc:creator>
      <dc:date>2006-06-12T22:41:10Z</dc:date>
    </item>
    <item>
      <title>Re: Setup virtual host with apache and ssl</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/setup-virtual-host-with-apache-and-ssl/m-p/4984917#M782946</link>
      <description>"apachectl startssl" only _allows_ you to use SSL, it does not _make_ the Apache servers use SSL. For that, you need some more configuration.&lt;BR /&gt;&lt;BR /&gt;Apache can handle having several SSL and non-SSL virtual hosts inside one Apache instance. You need to add the directive "SSLEngine on" for each SSL virtual host. You also need to specify a SSL certificate for them: the directive is "SSLCertificateFile /some/where/certificate.pem". You also need the private key for each certificate, which can be attached to the certificate or it can be a separate .pem file.&lt;BR /&gt;&lt;BR /&gt;With the OpenSSL tools, you can create a certificate for free, but it will be "untrusted" unless the browser is explicitly configured to trust that certificate. To get a certificate that will be trusted by any Web browser, you need to buy one from a Certification Authority like VeriSign.&lt;BR /&gt;&lt;BR /&gt;Currently, what you have is a simple set of HTTP virtual hosts in a non-standard port (i.e. 443).&lt;BR /&gt;&lt;BR /&gt;If you try an URL like &lt;A href="https://139.x.y.z1," target="_blank"&gt;https://139.x.y.z1,&lt;/A&gt; the browser tries to start up a SSL negotiation, which looks like a bunch of gibberish from a HTTP server viewpoint. The browser, on the other hand, sees the server's plain-HTTP error message as "some data that is not a valid SSL session". Because the SSL session did not get established, the only possible error message is going to be the browser's "could not establish a SSL connection", when the browser finally gives up on trying.&lt;BR /&gt;&lt;BR /&gt;In case you are trying name-based virtual hosting (several virtual hosts in the same IP address and TCP port), it does not work at all with HTTPS.&lt;BR /&gt;Basically, you have a chicken-and-egg problem: you need to know which virtual host the client wants to be able to offer the correct certificate, but that knowledge is in  the SSL-secured HTTPS request, which won't even get sent before the SSL encryption session is established.</description>
      <pubDate>Tue, 13 Jun 2006 03:00:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/setup-virtual-host-with-apache-and-ssl/m-p/4984917#M782946</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2006-06-13T03:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: Setup virtual host with apache and ssl</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/setup-virtual-host-with-apache-and-ssl/m-p/4984918#M782947</link>
      <description>Hi Matti,&lt;BR /&gt;Thanks for the info.  Just what I needed.  It is all so straight forward with the right key. &lt;BR /&gt;I have simply taken bits from ../conf/ssl./conf and included them with each virtual host and all work great.&lt;BR /&gt;Thankyou for your quick response.&lt;BR /&gt;David</description>
      <pubDate>Tue, 13 Jun 2006 17:27:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/setup-virtual-host-with-apache-and-ssl/m-p/4984918#M782947</guid>
      <dc:creator>David Woodroffe</dc:creator>
      <dc:date>2006-06-13T17:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: Setup virtual host with apache and ssl</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/setup-virtual-host-with-apache-and-ssl/m-p/4984919#M782948</link>
      <description>Reply indicated the correct solution to the problem.</description>
      <pubDate>Tue, 13 Jun 2006 17:30:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/setup-virtual-host-with-apache-and-ssl/m-p/4984919#M782948</guid>
      <dc:creator>David Woodroffe</dc:creator>
      <dc:date>2006-06-13T17:30:24Z</dc:date>
    </item>
  </channel>
</rss>

