<?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 Re: Apache https questions in Nuxeo Forum</title>
    <link>https://connect.hyland.com/t5/nuxeo-forum/apache-https-questions/m-p/324829#M11830</link>
    <description>&lt;P&gt;This is correct, Apache is the https endpoint then is reverse-proxying to nuxeo in http on the localhost interface. (it does not &lt;EM&gt;have&lt;/EM&gt; to be done that way, but that is what we found was the simplest).&lt;/P&gt;</description>
    <pubDate>Thu, 20 Mar 2014 11:00:24 GMT</pubDate>
    <dc:creator />
    <dc:date>2014-03-20T11:00:24Z</dc:date>
    <item>
      <title>Apache https questions</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/apache-https-questions/m-p/324828#M11829</link>
      <description>&lt;P&gt;If you saw my other thread, you'll know I'm doing the front end webserver as IIS.  I'm not a linux or Apache guy so...  Reading through the https Apache info, am I correct that:&lt;/P&gt;
&lt;P&gt;Https is only configured in Apache?&lt;BR /&gt; /&amp;gt;
You only load the cert to Apache?&lt;BR /&gt; /&amp;gt;
You don't have to enable 8443 in nuxeo/tomcat?&lt;BR /&gt; /&amp;gt;
Where the documentation says: 'RequestHeader append nuxeo-virtual-host "https://myDomainName/"' this is done in Apache?&lt;/P&gt;
&lt;P&gt;I think this is it.  Hopefully will help lead to a solution.  Currently the cert is installed in IIS and bound to 443.  Have the {http_host} configured and https:// works, but once you log in the internal paths are written as http as opposed to https and the browsers are complaining about loading unsecured content, since a full https rewrite isn't happening yet...&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2014 21:29:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/apache-https-questions/m-p/324828#M11829</guid>
      <dc:creator>vineyardtech_</dc:creator>
      <dc:date>2014-03-19T21:29:10Z</dc:date>
    </item>
    <item>
      <title>Re: Apache https questions</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/apache-https-questions/m-p/324829#M11830</link>
      <description>&lt;P&gt;This is correct, Apache is the https endpoint then is reverse-proxying to nuxeo in http on the localhost interface. (it does not &lt;EM&gt;have&lt;/EM&gt; to be done that way, but that is what we found was the simplest).&lt;/P&gt;</description>
      <pubDate>Thu, 20 Mar 2014 11:00:24 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/apache-https-questions/m-p/324829#M11830</guid>
      <dc:creator />
      <dc:date>2014-03-20T11:00:24Z</dc:date>
    </item>
    <item>
      <title>Re: Apache https questions</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/apache-https-questions/m-p/324830#M11831</link>
      <description>&lt;P&gt;Thanks.  Went through lots of files, configs, etc.  only to realize all that needed to be done in IIS was to replace {HTTP_HOST} in the url rewrite, with my https&lt;/P&gt;</description>
      <pubDate>Thu, 20 Mar 2014 17:51:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/apache-https-questions/m-p/324830#M11831</guid>
      <dc:creator>vineyardtech_</dc:creator>
      <dc:date>2014-03-20T17:51:23Z</dc:date>
    </item>
  </channel>
</rss>

