<?xml version='1.0' encoding='utf-8' ?>
<!--  If you are running a bot please visit this policy page outlining rules you must respect. https://www.livejournal.com/bots/  -->
<rss version='2.0'  xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:media='http://search.yahoo.com/mrss/' xmlns:atom10='http://www.w3.org/2005/Atom'>
<channel>
  <title>Apache Web Server Community</title>
  <link>https://apache.livejournal.com/</link>
  <description>Apache Web Server Community - LiveJournal.com</description>
  <lastBuildDate>Sun, 01 Aug 2010 21:02:10 GMT</lastBuildDate>
  <generator>LiveJournal / LiveJournal.com</generator>
  <lj:journal>apache</lj:journal>
  <lj:journalid>1400574</lj:journalid>
  <lj:journaltype>community</lj:journaltype>
  <image>
    <url>https://l-userpic.livejournal.com/7846387/1400574</url>
    <title>Apache Web Server Community</title>
    <link>https://apache.livejournal.com/</link>
    <width>100</width>
    <height>31</height>
  </image>

  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/44268.html</guid>
  <pubDate>Sun, 01 Aug 2010 21:02:10 GMT</pubDate>
  <title>Newb question about Struts2 &amp; JSP / Tomcat</title>
  <author>pkbarbiedoll</author>
  <link>https://apache.livejournal.com/44268.html</link>
  <description>&lt;span&gt;I&apos;m involved in migrating an existing, functional JSP/Struts2 app from Windows to Linux.&lt;br&gt; &lt;br&gt; The former Windows environment was a Tomcat/Struts/Eclipse setup. The new environment is a standalone installation of Tomcat (which is already configured and serving several other applications). &lt;br&gt; &lt;br&gt; The app in question, &quot;MyJSPWebsite&quot;, was copied to the Linux/Tomcat webapps folder and correct permissions assigned. The database (mysql) was also copied over with user permissions established. &lt;br&gt; &lt;br&gt; The site now opens, but none of the struts enabled content is functioning. For example, a drop-down list of data is not being populated. I&apos;m not seeing any error SQL messages in catalina.out, and the username/password &amp;amp; query work fine from command line. &lt;br&gt; &lt;br&gt; Are there separate, core struts files that have to be installed outside of those already included in the webapps/MyJSPWebsite folder?&lt;/span&gt;</description>
  <comments>https://apache.livejournal.com/44268.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>pkbarbiedoll</lj:poster>
  <lj:posterid>697617</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/43978.html</guid>
  <pubDate>Wed, 21 Oct 2009 20:37:44 GMT</pubDate>
  <title>Apache logs analysis</title>
  <author>catbegemot</author>
  <link>https://apache.livejournal.com/43978.html</link>
  <description>Hi all,&lt;br /&gt;I have a few servers that run suphp, so basically all incoming requests are logged in suphp_log. What I found amazing is that pretty much all malformed requests (like attempting to execute a javascript in improper places or scan for phpmyadmin scripts or something similar) are, pretty much, the only requests that are logged in access_log (except for WHM status requests).&lt;br /&gt;&lt;br /&gt;My question is - is there any automated tool that looks into access_log every now and then and comprises a report of such entries? I am no *nix admin, so I would appreciate any advise and leads.&lt;br /&gt;&lt;br /&gt;Thanks a lot!</description>
  <comments>https://apache.livejournal.com/43978.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>catbegemot</lj:poster>
  <lj:posterid>4264341</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/43634.html</guid>
  <pubDate>Tue, 20 Oct 2009 17:23:20 GMT</pubDate>
  <title>Redirect Match</title>
  <author>frazer</author>
  <link>https://apache.livejournal.com/43634.html</link>
  <description>Hello,&lt;br /&gt;&lt;br /&gt;i would like to do this:&lt;br /&gt;&lt;br /&gt;RedirectMatch 301 (.*)\.html$ $1&lt;br /&gt;RedirectMatch 301 (.*)\.htm$ $1&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;but not to files in sub folders.&lt;br /&gt;&lt;br /&gt;could some one please tell me how to do it?&lt;br /&gt;&lt;br /&gt;thank you</description>
  <comments>https://apache.livejournal.com/43634.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>frazer</lj:poster>
  <lj:posterid>721755</lj:posterid>
  <lj:reply-count>3</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/43049.html</guid>
  <pubDate>Tue, 07 Oct 2008 08:25:47 GMT</pubDate>
  <title>.htaccess works in http, not in https</title>
  <author>bendog</author>
  <link>https://apache.livejournal.com/43049.html</link>
  <description>Hi everybody,&lt;br /&gt;first time poster.&lt;br /&gt;&lt;br /&gt;This has me a little perplexed.&lt;br /&gt;I don&apos;t have shell access to this machine so i can&apos;t check logs and such to see what is actually going on, but my .htaccess script works fine under http, but it fails to accept the same password with https accesss.&lt;br /&gt;&lt;br /&gt;my thought is that perhaps there is some form of authentication difference, or perhaps i need to rebuild my .htpasswd file again.&lt;br /&gt;&lt;br /&gt;however this is my .htaccess file&lt;br /&gt;&lt;br /&gt;&lt;pre&gt;AuthUserFile /full/os/path/to/file/.htpasswd
AuthType Basic
AuthName &quot;Admin Folder&quot;
Require valid-user&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;any ideas?&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;---- UPDATED 2008:10:08 ----&lt;/b&gt;&lt;br /&gt;got this from their tech today.&lt;br /&gt;&lt;br /&gt;&amp;gt; Subject: Re: Re: Https and basic authentication under apache.&lt;br /&gt;&amp;gt;&lt;br /&gt;&amp;gt; haven&apos;t had any success as yet.&lt;br /&gt;&amp;gt;&lt;br /&gt;&amp;gt; the problem appears to be that the username is being &quot;lost&quot; when&lt;br /&gt;&amp;gt; authenticating via the SSL server.. (the error_log shows a &quot;blank&lt;br /&gt;&amp;gt; space&quot; where the username should be....)&lt;br /&gt;&amp;gt;</description>
  <comments>https://apache.livejournal.com/43049.html?view=comments#comments</comments>
  <media:title type="plain">Rocksteady Beats</media:title>
  <lj:music>Rocksteady Beats</lj:music>
  <lj:security>public</lj:security>
  <lj:poster>bendog</lj:poster>
  <lj:posterid>2206174</lj:posterid>
  <lj:reply-count>2</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/42827.html</guid>
  <pubDate>Fri, 19 Sep 2008 22:19:16 GMT</pubDate>
  <title>triggering mod_rewrite rule via auth failure?</title>
  <author>rekoil</author>
  <link>https://apache.livejournal.com/42827.html</link>
  <description>Hi,&lt;br /&gt;&lt;br /&gt;I&apos;m looking for a way to construct a RewriteCond that returns true only when a URL is requested without proper HTTP authentication. (The rewrite rule will generate a 301 redirect forcing the request through a proxy, where proper HTTP auth will allow direct access). So far, The Googles have not been helpful; anyone here have an idea?&lt;br /&gt;&lt;br /&gt;Effectively, I want &lt;br /&gt;&lt;br /&gt;&lt;a target=&apos;_blank&apos; href=&apos;http://user:pass@example.com/path/to/object&apos; rel=&apos;nofollow&apos;&gt;http://user:pass@example.com/path/to/object&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;to return the object directly, but &lt;br /&gt;&lt;br /&gt;&lt;a target=&apos;_blank&apos; href=&apos;http://user:badpass@example.com/path/to/object&apos; rel=&apos;nofollow&apos;&gt;http://user:badpass@example.com/path/to/object&lt;/a&gt;&lt;br /&gt;or&lt;br /&gt;&lt;a target=&apos;_blank&apos; href=&apos;http://example.com/path/to/object&apos; rel=&apos;nofollow&apos;&gt;http://example.com/path/to/object&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;will return a 301 to:&lt;br /&gt;&lt;br /&gt;&lt;a target=&apos;_blank&apos; href=&apos;http://proxy.example.com/path/to/object&apos; rel=&apos;nofollow&apos;&gt;http://proxy.example.com/path/to/object&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;(The proxy will use the proper u/p to access the server, so we won&apos;t have a redirect loop...)</description>
  <comments>https://apache.livejournal.com/42827.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>rekoil</lj:poster>
  <lj:posterid>674560</lj:posterid>
  <lj:reply-count>3</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/42093.html</guid>
  <pubDate>Wed, 25 Jun 2008 14:30:54 GMT</pubDate>
  <title>Confirming TRACE is off</title>
  <author>pkbarbiedoll</author>
  <link>https://apache.livejournal.com/42093.html</link>
  <description>Is there a non-telnet method of confirming whether TRACE is turned off?   I&apos;ve added TraceEnable off to my conf file but want to make sure everything is OK.    Telnet is disabled on my server.</description>
  <comments>https://apache.livejournal.com/42093.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>pkbarbiedoll</lj:poster>
  <lj:posterid>697617</lj:posterid>
  <lj:reply-count>1</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/41804.html</guid>
  <pubDate>Tue, 24 Jun 2008 22:17:33 GMT</pubDate>
  <title>Configuring SVN and Apache</title>
  <author>pkbarbiedoll</author>
  <link>https://apache.livejournal.com/41804.html</link>
  <description>svn came installed on my RHEL5 box and I am working on configuring the system for use with Apache. &lt;br /&gt;&lt;br /&gt;I am using the following tutorial: &lt;a target=&apos;_blank&apos; href=&apos;http://www.howtoforge.com/apache_subversion_repository_p2&apos; rel=&apos;nofollow&apos;&gt;http://www.howtoforge.com/apache_subversion_repository_p2&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Everything seemed OK (no errors) until the section &quot;Setting up the initial repository layout:&quot;.   When issuing the third command: &lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;svn import /tmp/subversion-layout/ &lt;a target=&apos;_blank&apos; href=&apos;http://127.0.0.1/subversion/&apos; rel=&apos;nofollow&apos;&gt;http://127.0.0.1/subversion/&lt;/a&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;The system returned the following error: &lt;br /&gt;&lt;br /&gt;[user@myserver directory]# svn import -m /tmp/svnmessage /tmp/subversion-layout/ &lt;a target=&apos;_blank&apos; href=&apos;http://127.0.0.1/subversion/&apos; rel=&apos;nofollow&apos;&gt;http://127.0.0.1/subversion/&lt;/a&gt;&lt;br /&gt;svn: PROPFIND request failed on &apos;/subversion&apos;&lt;br /&gt;svn: PROPFIND of &apos;/subversion&apos;: 405 Method Not Allowed (&lt;a target=&apos;_blank&apos; href=&apos;http://127.0.0.1&apos; rel=&apos;nofollow&apos;&gt;http://127.0.0.1&lt;/a&gt;)&lt;br /&gt;&lt;br /&gt;I did not restart apache before issing the svn import command - is that necessary?  Also, I created all of the directories as root.   Would that cause this problem?</description>
  <comments>https://apache.livejournal.com/41804.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>pkbarbiedoll</lj:poster>
  <lj:posterid>697617</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/41725.html</guid>
  <pubDate>Thu, 17 Apr 2008 11:45:15 GMT</pubDate>
  <title>Sporadic network timeouts</title>
  <author>pkbarbiedoll</author>
  <link>https://apache.livejournal.com/41725.html</link>
  <description>So, three sites are hosted on a single RHEL5 box, with Apache 2x serving pages.   Apache is using IP based virtual hosts.  &lt;br /&gt;&lt;br /&gt;Every once in a blue moon I try to access one of the sites and receive network timeout errors (doesn&apos;t matter if I access via IP or domain name).  The other two sites are still up and serving pages quickly - no slowdown or timeouts.&lt;br /&gt;&lt;br /&gt;After several minutes the network timeouts go away on their own.  &lt;br /&gt;&lt;br /&gt;Any ideas?&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;</description>
  <comments>https://apache.livejournal.com/41725.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>pkbarbiedoll</lj:poster>
  <lj:posterid>697617</lj:posterid>
  <lj:reply-count>3</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/41268.html</guid>
  <pubDate>Thu, 03 Apr 2008 20:38:09 GMT</pubDate>
  <title>Apache serving non-php files as php?</title>
  <author>muerte</author>
  <link>https://apache.livejournal.com/41268.html</link>
  <description>My server seems to think the following is PHP and serve it as such:&lt;br /&gt;&lt;br /&gt;&lt;a target=&apos;_blank&apos; href=&apos;http://www.perturb.org/tmp/test.php.foo.bar&apos;&gt;http://www.perturb.org/tmp/test.php.foo.bar&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;However... the same file (symlinked)&lt;br /&gt;&lt;br /&gt;&lt;a target=&apos;_blank&apos; href=&apos;http://www.perturb.org/tmp/test.php.txt&apos;&gt;http://www.perturb.org/tmp/test.php.txt&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Is served as text. In fact it appears that apache servers the content as whatever the &quot;last recognizable&quot; extension. Shouldn&apos;t apache only server files that END in .php as php files?&lt;br /&gt;&lt;br /&gt;The configuration is very simple:&lt;br /&gt;&lt;br /&gt;AddType application/x-httpd-php .php&lt;br /&gt;AddType application/x-httpd-php-source .phps</description>
  <comments>https://apache.livejournal.com/41268.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>muerte</lj:poster>
  <lj:posterid>1806</lj:posterid>
  <lj:reply-count>2</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/41133.html</guid>
  <pubDate>Wed, 05 Mar 2008 14:25:44 GMT</pubDate>
  <title>Apache SSL, removing passphrase prompt</title>
  <author>pkbarbiedoll</author>
  <link>https://apache.livejournal.com/41133.html</link>
  <description>&lt;span&gt;When my system reboots Apache needs the passphrase to start. I&apos;d like to remove this prompt so the server can start without human intervention. So, according to the docs I can do this: &lt;br /&gt; &lt;br /&gt; openssl rsa -in server.key.current -out server.key.new&lt;br /&gt; &lt;br /&gt;But I wasn&apos;t prompted to enter my passphrase when issuing this command.&amp;nbsp; The resulting outfile is identical to server.key.current. &lt;br /&gt; Suggestions?&lt;/span&gt;</description>
  <comments>https://apache.livejournal.com/41133.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>pkbarbiedoll</lj:poster>
  <lj:posterid>697617</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/40776.html</guid>
  <pubDate>Wed, 05 Mar 2008 09:50:30 GMT</pubDate>
  <author>ne_zanimatj</author>
  <link>https://apache.livejournal.com/40776.html</link>
  <description>Good day,&lt;br /&gt;Can I somehow set specific virtualhost for resolving of unregistered in our system domains?&lt;br /&gt;&lt;br /&gt;Thanks</description>
  <comments>https://apache.livejournal.com/40776.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>ne_zanimatj</lj:poster>
  <lj:posterid>1071067</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/40574.html</guid>
  <pubDate>Mon, 03 Mar 2008 19:43:21 GMT</pubDate>
  <title>IE7 cert mismatch errors</title>
  <author>pkbarbiedoll</author>
  <link>https://apache.livejournal.com/40574.html</link>
  <description>  &lt;p class=&quot;&quot;&gt;&lt;span style=&quot;color: black;&quot;&gt;Some of our IE7 users receive security certificate mismatch warnings with every secure page view on &lt;u&gt;subdomain.domain.net&lt;/u&gt;.&lt;span&gt;&amp;nbsp; &lt;/span&gt;The cert was originally issued to &lt;/span&gt;&lt;u&gt;&lt;span style=&quot;color: black;&quot;&gt;www.domain.net&lt;/span&gt;&lt;/u&gt;&lt;span style=&quot;color: black;&quot;&gt;.&lt;span&gt;&amp;nbsp; &lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p class=&quot;&quot;&gt;&amp;nbsp;&lt;/p&gt;&lt;p class=&quot;&quot;&gt;Is it possible to add aliases to existing certificates (my hunch is no, but I&apos;m not well versed on them)?&amp;nbsp; &lt;span style=&quot;color: black;&quot;&gt;&lt;span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p class=&quot;&quot;&gt;&lt;span style=&quot;color: black;&quot;&gt;&lt;span&gt;&lt;/span&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;</description>
  <comments>https://apache.livejournal.com/40574.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>pkbarbiedoll</lj:poster>
  <lj:posterid>697617</lj:posterid>
  <lj:reply-count>1</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/39707.html</guid>
  <pubDate>Fri, 21 Dec 2007 17:13:41 GMT</pubDate>
  <title>404 for user pages</title>
  <author>christtrekker</author>
  <link>https://apache.livejournal.com/39707.html</link>
  <description>I&apos;ve thought of adding MediaWiki to my site just to make it super easy to add content whenever I wanted.  I know I could make Apache serve the wiki user page if the ~username URL was requested, but is it possible to make it do that only if it couldn&apos;t be found in the more traditional location (like his home dir) first?  Would that require some kind of handler script?</description>
  <comments>https://apache.livejournal.com/39707.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>christtrekker</lj:poster>
  <lj:posterid>2118849</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/39386.html</guid>
  <pubDate>Wed, 14 Nov 2007 18:50:45 GMT</pubDate>
  <title>Apache Con</title>
  <author>walkingbear</author>
  <link>https://apache.livejournal.com/39386.html</link>
  <description>Anyone here in Atlanta at ApacheCon?&lt;br /&gt;&lt;br /&gt;Look for the guy in black with the pipe in one hand and a book in the other.  That&apos;s me.</description>
  <comments>https://apache.livejournal.com/39386.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>walkingbear</lj:poster>
  <lj:posterid>925393</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/38750.html</guid>
  <pubDate>Tue, 11 Sep 2007 15:02:54 GMT</pubDate>
  <title>Analytics</title>
  <author>pkbarbiedoll</author>
  <link>https://apache.livejournal.com/38750.html</link>
  <description>Our project is interested in buying a solid analytics application for several sites hosted on an Apache server.&amp;nbsp;&amp;nbsp; What are our best options?</description>
  <comments>https://apache.livejournal.com/38750.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>pkbarbiedoll</lj:poster>
  <lj:posterid>697617</lj:posterid>
  <lj:reply-count>1</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/38566.html</guid>
  <pubDate>Mon, 27 Aug 2007 18:42:12 GMT</pubDate>
  <title>FilesMatch</title>
  <author>mausolos</author>
  <link>https://apache.livejournal.com/38566.html</link>
  <description>I want to generate links with my code like &quot;index_flotsam.php&quot; and &quot;index_jetsam.php&quot; and have apache ignore everything but &quot;index.php&quot;.  So if the user clicks on &quot;index_flotsam.php&quot; it will just take them to the file &quot;index.php&quot; but will still display the url &quot;index_flotsam.php&quot;.  I&apos;m using Apache 2.2.4.  I have a feeling I could probably do this with the FilesMatch directive, but I&apos;m not entirely sure how.  Any ideas?&lt;br /&gt;&lt;br /&gt;Thanks!</description>
  <comments>https://apache.livejournal.com/38566.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>mausolos</lj:poster>
  <lj:posterid>1085963</lj:posterid>
  <lj:reply-count>4</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/38398.html</guid>
  <pubDate>Thu, 28 Jun 2007 14:34:23 GMT</pubDate>
  <title>Problem with verisign cert</title>
  <author>pkbarbiedoll</author>
  <link>https://apache.livejournal.com/38398.html</link>
  <description>We bought a certificate for a domain. &amp;nbsp; I&apos;ve set up a few sites with ssl before this, so I was careful to enter the FQDN in my csr request.&amp;nbsp; A day later Verisign sent the cert in an email, which we copied into a sitename.crt file on the server.&amp;nbsp;&amp;nbsp; I made an unecrypted version of the key so I wouldn&apos;t have to enter the passphrase every time Apache starts.&amp;nbsp; (yes I entered the passphrase, which was accepted)&lt;br /&gt;&lt;br /&gt;So - I start the server without errors.&amp;nbsp; When I access the site using &lt;a target=&apos;_blank&apos; href=&apos;https://sitename&apos; rel=&apos;nofollow&apos;&gt;https://sitename&lt;/a&gt;, the browser returns a certificate mismatch error.&amp;nbsp;&amp;nbsp; The cert details appear with localhost, localdomain, ect, which is not what I entered when creating the csr &amp;amp; key.&amp;nbsp; &lt;br /&gt;&lt;br /&gt;&amp;lt;VirtualHost 1.2.3.4:443&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ServerName sitename.department.domain.ext&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ServerAdmin abc@123.def&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; DocumentRoot /www/virtualhosts/sitename&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ErrorLog /var/log/httpd/sitename-error_log&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; CustomLog /var/log/httpd/sitename-access_log common&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; SSLEngine On&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; SSLCertificateFile /usr/local/ssl/crt/sitename.crt&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; SSLCertificateKeyFile /usr/local/ssl/crt/sitename_unencrypted.key&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; SSLCACertificateFile /usr/local/ssl/crt/intermediate.crt&lt;br /&gt;&amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Is there a way to print out the details listed in a crt file, from command line?&amp;nbsp;&amp;nbsp; Can I do the same with the original csr file?&amp;nbsp;&amp;nbsp;</description>
  <comments>https://apache.livejournal.com/38398.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>pkbarbiedoll</lj:poster>
  <lj:posterid>697617</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/37811.html</guid>
  <pubDate>Thu, 21 Jun 2007 00:30:39 GMT</pubDate>
  <title>Apache 2.2.4 and Vista</title>
  <author>mausolos</author>
  <link>https://apache.livejournal.com/37811.html</link>
  <description>I guess lots of people (including me) are having problems getting Apache to work on Vista.  I don&apos;t know if anyone&apos;s already posted this solution, but I pieced it together from a few different sites that each offered their own little tidbit.  I hope this helps someone:&lt;br /&gt;&lt;br /&gt;1) if you have already been trying to make this work, make sure you completely remove and detele all evidence of apache 2.2.4 from your computer: program files, registry, etc.  if you haven&apos;t had a failed install attempt and you&apos;re starting fresh, go on to step 2.&lt;br /&gt;2) turn off User Access Control&lt;br /&gt;2) run cmd.exe as an administrator.  you can do this by right-clicking on the link in the start menu program list.&lt;br /&gt;3) from the command line, go to the directory your apache msi file is in.  enter: &quot;msiexec /i &lt;apache_filename&gt;.msi&quot; (without the quotes obviously)&lt;br /&gt;5) let the program run, check off everything as you see fit.  when the program has finished running, it will most likely display an error popup.  close this.&lt;br /&gt;6) back on the command line (still running as administrator), go to &lt;your_apache_directory&gt;\bin and enter: &quot;httpd -k install&quot;&lt;br /&gt;7) now apache should show up as a service.  but you&apos;re not done yet!  go to the apache monitor/control thingy in your start menu.  right-click it and go to properties-&amp;gt;compatibility.  set the compatibility mode to winxp sp2.&lt;br /&gt;8) that&apos;s it!  you may want to start your apache control, but it will run now without that.</description>
  <comments>https://apache.livejournal.com/37811.html?view=comments#comments</comments>
  <media:title type="plain">As High As You Can Go (Chameleons U.K.)</media:title>
  <lj:music>As High As You Can Go (Chameleons U.K.)</lj:music>
  <lj:mood>blah</lj:mood>
  <lj:security>public</lj:security>
  <lj:poster>mausolos</lj:poster>
  <lj:posterid>1085963</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/37226.html</guid>
  <pubDate>Tue, 12 Jun 2007 14:15:03 GMT</pubDate>
  <title>Virtual hosting - testing</title>
  <author>pkbarbiedoll</author>
  <link>https://apache.livejournal.com/37226.html</link>
  <description>I created two name-based virtual hosts&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;    NameVirtualHost *:80&lt;br /&gt;    &lt;br /&gt;    &amp;lt;VirtualHost *:80&amp;gt;&lt;br /&gt;    ServerName siteone.subX.subY.com&lt;br /&gt;    ServerAdmin me@me.com&lt;br /&gt;    DocumentRoot /www/virtualhosts/siteone&lt;br /&gt;    ErrorLog /var/log/httpd/siteone-error_log&lt;br /&gt;    CustomLog /var/log/httpd/siteone-access_log common&lt;br /&gt;&amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;&lt;br /&gt;&amp;lt;VirtualHost *:80&amp;gt;&lt;br /&gt;    ServerName sitetwo.subX.subY.com&lt;br /&gt;    ServerAdmin me@me.com&lt;br /&gt;    DocumentRoot /www/virtualhosts/sitetwo&lt;br /&gt;    ErrorLog /var/log/httpd/sitetwo-error_log&lt;br /&gt;    CustomLog /var/log/httpd/sitetwo-access_log common&lt;br /&gt;&amp;lt;/VirtualHost&amp;gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Shouldn&apos;t I be able to test them by adding entries in my local hosts file, and accessing via &lt;a target=&apos;_blank&apos; href=&apos;http://sitetwo.subX.subY.com&apos; rel=&apos;nofollow&apos;&gt;http://sitetwo.subX.subY.com&lt;/a&gt;?  Well, when I do that, the site that displays is actually site&lt;strong&gt;one&lt;/strong&gt;.subX.subY.com.   So it&apos;s always displaying the default VH, no matter what domain I use.</description>
  <comments>https://apache.livejournal.com/37226.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>pkbarbiedoll</lj:poster>
  <lj:posterid>697617</lj:posterid>
  <lj:reply-count>4</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/37060.html</guid>
  <pubDate>Mon, 11 Jun 2007 19:28:22 GMT</pubDate>
  <title>Seperate instances of Apache under one box</title>
  <author>pkbarbiedoll</author>
  <link>https://apache.livejournal.com/37060.html</link>
  <description>Can Apache run under different instances, so that we can direct traffic to each Virtual Host under a different instance.   Would doing so offer better security than simply using virtual hosting?   One of our sites is internal, the others are public.  We want to keep the internal site locked down extremely tight.  &lt;br /&gt;&lt;br /&gt;In that same light, is it possible to have different SSL certs for different Virtual Hosts running on the same physical box (under one IP)? &lt;br /&gt;&lt;br /&gt;Thanks for suggestions/pointers.</description>
  <comments>https://apache.livejournal.com/37060.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>pkbarbiedoll</lj:poster>
  <lj:posterid>697617</lj:posterid>
  <lj:reply-count>7</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/36714.html</guid>
  <pubDate>Fri, 11 May 2007 02:06:58 GMT</pubDate>
  <author>subtle_rift</author>
  <link>https://apache.livejournal.com/36714.html</link>
  <description>Suppose I had various servers for different types of content sitting behing an Apache server.  Firstly, am I right in thinking I can configure Apache to connect to the relevant computer when everything&apos;s static?  Secondly, what if things moved dynamicaly, for example if I maintained a dynamic cache, either on the same or a different machine to the one running Apache.  Where Apache should look for a given resource would be specified by an external program.  Can I do this?  I&apos;d need to be able to pass the external program not just the http request but also and session variables.&lt;br /&gt;&lt;br /&gt;Cheers</description>
  <comments>https://apache.livejournal.com/36714.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>subtle_rift</lj:poster>
  <lj:posterid>6318169</lj:posterid>
  <lj:reply-count>1</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/35679.html</guid>
  <pubDate>Mon, 05 Feb 2007 13:38:11 GMT</pubDate>
  <title>Prevent Multiple Logins/Concurrent logins</title>
  <author>tl56</author>
  <link>https://apache.livejournal.com/35679.html</link>
  <description>Hello &lt;br /&gt;I would like to limit the number of times a user can login into my portal.&lt;br /&gt;Thus, if the user is currently logged in when he/she attempts to login again we&lt;br /&gt;want to prevent them from logging in hence limit one login per user. Or if you know of the way to disconnect the first login and allow the second login. &lt;br /&gt;For ex:&lt;br /&gt;the user logs in on one machine then goes to another machine and logs in again while the other session is still active. I need to make it so when the second login attempt is made it is denied since there is already an active connection with that username and password.</description>
  <comments>https://apache.livejournal.com/35679.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>tl56</lj:poster>
  <lj:posterid>12212926</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/35519.html</guid>
  <pubDate>Sun, 26 Nov 2006 23:29:07 GMT</pubDate>
  <title>Apache2 &amp; Openssl</title>
  <author>pkbarbiedoll</author>
  <link>https://apache.livejournal.com/35519.html</link>
  <description>Ok I have Apache2 and openssl working -- mostly.&amp;nbsp; Apache starts without issue, and when I go to localhost:443 I have a little lock in my address bar.&amp;nbsp;  My problem is that files in my &apos;secure&apos; htdocs folder (as specified in ssl.conf) do not exist, according to apache. &lt;br /&gt;&lt;br /&gt;I&apos;ve never installed a secure server so I may be missing something obvious - any help with this is greatly appreciated. &lt;br /&gt;&lt;br /&gt;Config files beneath the cut: &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;SSL.CONF&lt;br /&gt;#&lt;br /&gt;# This is the Apache server configuration file providing SSL support.&lt;br /&gt;# It contains the configuration directives to instruct the server how to&lt;br /&gt;# serve pages over an https connection. For detailing information about these &lt;br /&gt;# directives see &amp;lt;url:http://httpd.apache.org/docs-2.0/mod/mod_ssl.html&amp;gt;&lt;br /&gt;#&lt;br /&gt;#&amp;nbsp;  For the moment, see &amp;lt;url:http://www.modssl.org/docs/&amp;gt; for this info. &lt;br /&gt;#&amp;nbsp;  The documents are still being prepared from material donated by the&lt;br /&gt;#&amp;nbsp;  modssl project.&lt;br /&gt;# &lt;br /&gt;# Do NOT simply read the instructions in here without understanding&lt;br /&gt;# what they do.&amp;nbsp; They&apos;re here only as hints or reminders.&amp;nbsp; If you are unsure&lt;br /&gt;# consult the online docs. You have been warned.&amp;nbsp; &lt;br /&gt;#&lt;br /&gt;&lt;br /&gt;#&lt;ifdefine ssl=&quot;SSL&quot;&gt;&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Until documentation is completed, please check &lt;a target=&apos;_blank&apos; href=&apos;http://www.modssl.org/&apos; rel=&apos;nofollow&apos;&gt;http://www.modssl.org/&lt;/a&gt;&lt;br /&gt;#&amp;nbsp;  for additional config examples and module docmentation.&amp;nbsp; Directives&lt;br /&gt;#&amp;nbsp;  and features of mod_ssl are largely unchanged from the mod_ssl project&lt;br /&gt;#&amp;nbsp;  for Apache 1.3.&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# When we also provide SSL we have to listen to the &lt;br /&gt;# standard HTTP port (see above) and to the HTTPS port&lt;br /&gt;#&lt;br /&gt;Listen 443&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Dynamic Shared Object (DSO) Support&lt;br /&gt;#&lt;br /&gt;# To be able to use the functionality of a module which was built as a DSO you&lt;br /&gt;#&amp;nbsp; &amp;nbsp; ErrorLog logs/dummy-host.example.com-error_log&lt;br /&gt;#&amp;nbsp; &amp;nbsp; CustomLog logs/dummy-host.example.com-access_log common&lt;br /&gt;&lt;br /&gt;##&lt;br /&gt;##&amp;nbsp; SSL Global Context&lt;br /&gt;##&lt;br /&gt;##&amp;nbsp; All SSL configuration in this context applies both to&lt;br /&gt;##&amp;nbsp; the main server and all SSL-enabled virtual hosts.&lt;br /&gt;##&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;#&amp;nbsp;  Some MIME-types for downloading Certificates and CRLs&lt;br /&gt;#&lt;br /&gt;AddType application/x-x509-ca-cert .crt&lt;br /&gt;AddType application/x-pkcs7-crl&amp;nbsp; &amp;nbsp; .crl&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Pass Phrase Dialog:&lt;br /&gt;#&amp;nbsp;  Configure the pass phrase gathering process.&lt;br /&gt;#&amp;nbsp;  The filtering dialog program (`builtin&apos; is a internal&lt;br /&gt;#&amp;nbsp;  terminal dialog) has to provide the pass phrase on stdout.&lt;br /&gt;SSLPassPhraseDialog&amp;nbsp; builtin&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Inter-Process Session Cache:&lt;br /&gt;#&amp;nbsp;  Configure the SSL Session Cache: First the mechanism &lt;br /&gt;#&amp;nbsp;  to use and second the expiring timeout (in seconds).&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLSessionCache&apos;&gt;#SSLSessionCache&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; none&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLSessionCache&apos;&gt;#SSLSessionCache&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; shmht:logs/ssl_scache(512000)&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLSessionCache&apos;&gt;#SSLSessionCache&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; shmcb:logs/ssl_scache(512000)&lt;br /&gt;SSLSessionCache&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;  dbm:logs/ssl-scache.log&lt;br /&gt;SSLSessionCacheTimeout&amp;nbsp; 300&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Semaphore:&lt;br /&gt;#&amp;nbsp;  Configure the path to the mutual exclusion semaphore the&lt;br /&gt;#&amp;nbsp;  SSL engine uses internally for inter-process synchronization. &lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLMutex&apos;&gt;#SSLMutex&lt;/a&gt;&amp;nbsp; file:logs/ssl_mutex.log&lt;br /&gt;SSLMutex default&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Pseudo Random Number Generator (PRNG):&lt;br /&gt;#&amp;nbsp;  Configure one or more sources to seed the PRNG of the &lt;br /&gt;#&amp;nbsp;  SSL library. The seed data should be of good random quality.&lt;br /&gt;#&amp;nbsp;  WARNING! On some platforms /dev/random blocks if not enough entropy&lt;br /&gt;#&amp;nbsp;  is available. This means you then cannot use the /dev/random device&lt;br /&gt;#&amp;nbsp;  because it would lead to very long connection times (as long as&lt;br /&gt;#&amp;nbsp;  it requires to make more entropy available). But usually those&lt;br /&gt;#&amp;nbsp;  platforms additionally provide a /dev/urandom device which doesn&apos;t&lt;br /&gt;#&amp;nbsp;  block. So, if available, use this one instead. Read the mod_ssl User&lt;br /&gt;#&amp;nbsp;  Manual for more details.&lt;br /&gt;SSLRandomSeed startup builtin&lt;br /&gt;SSLRandomSeed connect builtin&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLRandomSeed&apos;&gt;#SSLRandomSeed&lt;/a&gt; startup file:/dev/random&amp;nbsp; 512&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLRandomSeed&apos;&gt;#SSLRandomSeed&lt;/a&gt; startup file:/dev/urandom 512&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLRandomSeed&apos;&gt;#SSLRandomSeed&lt;/a&gt; connect file:/dev/random&amp;nbsp; 512&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLRandomSeed&apos;&gt;#SSLRandomSeed&lt;/a&gt; connect file:/dev/urandom 512&lt;br /&gt;&lt;br /&gt;##&lt;br /&gt;## SSL Virtual Host Context&lt;br /&gt;##&lt;br /&gt;&lt;br /&gt;&lt;virtualhost _default_:443=&quot;_default_:443&quot;&gt;&lt;br /&gt;&lt;br /&gt;#&amp;nbsp; General setup for the virtual host&lt;br /&gt;DocumentRoot &quot;C:\Program Files\Apache Group\Apache2\htdocs_secure&quot;&lt;br /&gt;ServerName localhost:443&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23ServerName&apos;&gt;#ServerName&lt;/a&gt; www.my-domain.com:443&lt;br /&gt;ServerAdmin you@your.address&lt;br /&gt;ErrorLog logs/error.log&lt;br /&gt;TransferLog logs/access.log&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  SSL Engine Switch:&lt;br /&gt;#&amp;nbsp;  Enable/Disable SSL for this virtual host.&lt;br /&gt;SSLEngine on&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  SSL Cipher Suite:&lt;br /&gt;#&amp;nbsp;  List the ciphers that the client is permitted to negotiate.&lt;br /&gt;#&amp;nbsp;  See the mod_ssl documentation for a complete list.&lt;br /&gt;SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Server Certificate:&lt;br /&gt;#&amp;nbsp;  Point SSLCertificateFile at a PEM encoded certificate.&amp;nbsp; If&lt;br /&gt;#&amp;nbsp;  the certificate is encrypted, then you will be prompted for a&lt;br /&gt;#&amp;nbsp;  pass phrase.&amp;nbsp; Note that a kill -HUP will prompt again.&amp;nbsp; Keep&lt;br /&gt;#&amp;nbsp;  in mind that if you have both an RSA and a DSA certificate you&lt;br /&gt;#&amp;nbsp;  can configure both in parallel (to also allow the use of DSA&lt;br /&gt;#&amp;nbsp;  ciphers, etc.)&lt;br /&gt;SSLCertificateFile conf/ssl/my-server.cert&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLCertificateFile&apos;&gt;#SSLCertificateFile&lt;/a&gt; conf/ssl.crt/server-dsa.crt&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Server Private Key:&lt;br /&gt;#&amp;nbsp;  If the key is not combined with the certificate, use this&lt;br /&gt;#&amp;nbsp;  directive to point at the key file.&amp;nbsp; Keep in mind that if&lt;br /&gt;#&amp;nbsp;  you&apos;ve both a RSA and a DSA private key you can configure&lt;br /&gt;#&amp;nbsp;  both in parallel (to also allow the use of DSA ciphers, etc.)&lt;br /&gt;SSLCertificateKeyFile conf/ssl/my-server.key&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLCertificateKeyFile&apos;&gt;#SSLCertificateKeyFile&lt;/a&gt; conf/ssl.key/server-dsa.key&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Server Certificate Chain:&lt;br /&gt;#&amp;nbsp;  Point SSLCertificateChainFile at a file containing the&lt;br /&gt;#&amp;nbsp;  concatenation of PEM encoded CA certificates which form the&lt;br /&gt;#&amp;nbsp;  certificate chain for the server certificate. Alternatively&lt;br /&gt;#&amp;nbsp;  the referenced file can be the same as SSLCertificateFile&lt;br /&gt;#&amp;nbsp;  when the CA certificates are directly appended to the server&lt;br /&gt;#&amp;nbsp;  certificate for convinience.&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLCertificateChainFile&apos;&gt;#SSLCertificateChainFile&lt;/a&gt; conf/ssl.crt/ca.crt&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Certificate Authority (CA):&lt;br /&gt;#&amp;nbsp;  Set the CA certificate verification path where to find CA&lt;br /&gt;#&amp;nbsp;  certificates for client authentication or alternatively one&lt;br /&gt;#&amp;nbsp;  huge file containing all of them (file must be PEM encoded)&lt;br /&gt;#&amp;nbsp;  Note: Inside SSLCACertificatePath you need hash symlinks&lt;br /&gt;#&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;  to point to the certificate files. Use the provided&lt;br /&gt;#&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;  Makefile to update the hash symlinks after changes.&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLCACertificatePath&apos;&gt;#SSLCACertificatePath&lt;/a&gt; conf/ssl.crt&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLCACertificateFile&apos;&gt;#SSLCACertificateFile&lt;/a&gt; conf/ssl.crt/ca-bundle.crt&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Certificate Revocation Lists (CRL):&lt;br /&gt;#&amp;nbsp;  Set the CA revocation path where to find CA CRLs for client&lt;br /&gt;#&amp;nbsp;  authentication or alternatively one huge file containing all&lt;br /&gt;#&amp;nbsp;  of them (file must be PEM encoded)&lt;br /&gt;#&amp;nbsp;  Note: Inside SSLCARevocationPath you need hash symlinks&lt;br /&gt;#&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;  to point to the certificate files. Use the provided&lt;br /&gt;#&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;  Makefile to update the hash symlinks after changes.&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLCARevocationPath&apos;&gt;#SSLCARevocationPath&lt;/a&gt; conf/ssl.crl&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLCARevocationFile&apos;&gt;#SSLCARevocationFile&lt;/a&gt; conf/ssl.crl/ca-bundle.crl&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Client Authentication (Type):&lt;br /&gt;#&amp;nbsp;  Client certificate verification type and depth.&amp;nbsp; Types are&lt;br /&gt;#&amp;nbsp;  none, optional, require and optional_no_ca.&amp;nbsp; Depth is a&lt;br /&gt;#&amp;nbsp;  number which specifies how deeply to verify the certificate&lt;br /&gt;#&amp;nbsp;  issuer chain before deciding the certificate is not valid.&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLVerifyClient&apos;&gt;#SSLVerifyClient&lt;/a&gt; require&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLVerifyDepth&apos;&gt;#SSLVerifyDepth&lt;/a&gt;&amp;nbsp; 10&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  Access Control:&lt;br /&gt;#&amp;nbsp;  With SSLRequire you can do per-directory access control based&lt;br /&gt;#&amp;nbsp;  on arbitrary complex boolean expressions containing server&lt;br /&gt;#&amp;nbsp;  variable checks and other lookup directives.&amp;nbsp; The syntax is a&lt;br /&gt;#&amp;nbsp;  mixture between C and Perl.&amp;nbsp; See the mod_ssl documentation&lt;br /&gt;#&amp;nbsp;  for more details.&lt;br /&gt;#&lt;location&gt;&lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLRequire&apos;&gt;#SSLRequire&lt;/a&gt; (&amp;nbsp; &amp;nbsp; %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \&lt;br /&gt;#&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; and %{SSL_CLIENT_S_DN_O} eq &quot;Snake Oil, Ltd.&quot; \&lt;br /&gt;#&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; and %{SSL_CLIENT_S_DN_OU} in {&quot;Staff&quot;, &quot;CA&quot;, &quot;Dev&quot;} \&lt;br /&gt;#&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; and %{TIME_WDAY} &amp;gt;= 1 and %{TIME_WDAY} &amp;lt;= 5 \&lt;br /&gt;#&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; and %{TIME_HOUR} &amp;gt;= 8 and %{TIME_HOUR} &amp;lt;= 20&amp;nbsp; &amp;nbsp; &amp;nbsp;  ) \&lt;br /&gt;#&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;  or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/&lt;br /&gt;#&lt;/location&gt;&lt;br /&gt;&lt;br /&gt;#&amp;nbsp;  SSL Engine Options:&lt;br /&gt;#&amp;nbsp;  Set various options for the SSL engine.&lt;br /&gt;#&amp;nbsp;  o FakeBasicAuth:&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  Translate the client X.509 into a Basic Authorisation.&amp;nbsp; This means that&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  the standard Auth/DBMAuth methods can be used for access control.&amp;nbsp; The&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  user name is the `one line&apos; version of the client&apos;s X.509 certificate.&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  Note that no password is obtained from the user. Every entry in the user&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  file needs this password: `xxj31ZMTZzkVA&apos;.&lt;br /&gt;#&amp;nbsp;  o ExportCertData:&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  This exports two additional environment variables: SSL_CLIENT_CERT and&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  SSL_SERVER_CERT. These contain the PEM-encoded certificates of the&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  server (always existing) and the client (only existing when client&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  authentication is used). This can be used to import the certificates&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  into CGI scripts.&lt;br /&gt;#&amp;nbsp;  o StdEnvVars:&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  This exports the standard SSL/TLS related `SSL_*&apos; environment variables.&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  Per default this exportation is switched off for performance reasons,&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  because the extraction step is an expensive operation and is usually&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  useless for serving static content. So one usually enables the&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  exportation for CGI and SSI requests only.&lt;br /&gt;#&amp;nbsp;  o CompatEnvVars:&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  This exports obsolete environment variables for backward compatibility&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  to Apache-SSL 1.x, mod_ssl 2.0.x, Sioux 1.0 and Stronghold 2.x. Use this&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  to provide compatibility to existing CGI scripts.&lt;br /&gt;#&amp;nbsp;  o StrictRequire:&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  This denies access when &quot;SSLRequireSSL&quot; or &quot;SSLRequire&quot; applied even&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  under a &quot;Satisfy any&quot; situation, i.e. when it applies access is denied&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  and no other module can change it.&lt;br /&gt;#&amp;nbsp;  o OptRenegotiate:&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  This enables optimized SSL connection renegotiation handling when SSL&lt;br /&gt;#&amp;nbsp; &amp;nbsp;  directives are used in per-directory context. &lt;br /&gt;&lt;a href=&apos;https://www.livejournal.com/rsearch/?tags=%23SSLOptions&apos;&gt;#SSLOptions&lt;/a&gt; +FakeBasicAuth +ExportCertData +CompatEnvVars +StrictRequire&lt;br /&gt;&lt;div class=&apos;ljparseerror&apos;&gt;[&lt;b&gt;Error:&lt;/b&gt; Irreparable invalid markup (&apos;&amp;lt;files [...] &amp;#126;&amp;gt;&apos;) in entry.  Owner must fix manually.  Raw contents below.]&lt;br /&gt;&lt;br /&gt;&lt;div style=&quot;width: 95%; overflow: auto&quot;&gt;Ok I have Apache2 and openssl working -- mostly.&amp;amp;nbsp; Apache starts without issue, and when I go to localhost:443 I have a little lock in my address bar.&amp;amp;nbsp;  My problem is that files in my &amp;#39;secure&amp;#39; htdocs folder (as specified in ssl.conf) do not exist, according to apache. &lt;br /&gt;&lt;br /&gt;I&amp;#39;ve never installed a secure server so I may be missing something obvious - any help with this is greatly appreciated. &lt;br /&gt;&lt;br /&gt;Config files beneath the cut: &lt;br /&gt;&lt;br /&gt;&amp;lt;lj-cut text=&amp;quot;ssl.conf&amp;quot;&amp;gt;&lt;br /&gt;SSL.CONF&lt;br /&gt;#&lt;br /&gt;# This is the Apache server configuration file providing SSL support.&lt;br /&gt;# It contains the configuration directives to instruct the server how to&lt;br /&gt;# serve pages over an https connection. For detailing information about these &lt;br /&gt;# directives see &amp;lt;URL:http://httpd.apache.org/docs-2.0/mod/mod_ssl.html&amp;gt;&lt;br /&gt;#&lt;br /&gt;#&amp;amp;nbsp;  For the moment, see &amp;lt;URL:http://www.modssl.org/docs/&amp;gt; for this info. &lt;br /&gt;#&amp;amp;nbsp;  The documents are still being prepared from material donated by the&lt;br /&gt;#&amp;amp;nbsp;  modssl project.&lt;br /&gt;# &lt;br /&gt;# Do NOT simply read the instructions in here without understanding&lt;br /&gt;# what they do.&amp;amp;nbsp; They&amp;#39;re here only as hints or reminders.&amp;amp;nbsp; If you are unsure&lt;br /&gt;# consult the online docs. You have been warned.&amp;amp;nbsp; &lt;br /&gt;#&lt;br /&gt;&lt;br /&gt;#&amp;lt;IfDefine SSL&amp;gt;&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Until documentation is completed, please check http://www.modssl.org/&lt;br /&gt;#&amp;amp;nbsp;  for additional config examples and module docmentation.&amp;amp;nbsp; Directives&lt;br /&gt;#&amp;amp;nbsp;  and features of mod_ssl are largely unchanged from the mod_ssl project&lt;br /&gt;#&amp;amp;nbsp;  for Apache 1.3.&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# When we also provide SSL we have to listen to the &lt;br /&gt;# standard HTTP port (see above) and to the HTTPS port&lt;br /&gt;#&lt;br /&gt;Listen 443&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Dynamic Shared Object (DSO) Support&lt;br /&gt;#&lt;br /&gt;# To be able to use the functionality of a module which was built as a DSO you&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorLog logs/dummy-host.example.com-error_log&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; CustomLog logs/dummy-host.example.com-access_log common&lt;br /&gt;&lt;br /&gt;##&lt;br /&gt;##&amp;amp;nbsp; SSL Global Context&lt;br /&gt;##&lt;br /&gt;##&amp;amp;nbsp; All SSL configuration in this context applies both to&lt;br /&gt;##&amp;amp;nbsp; the main server and all SSL-enabled virtual hosts.&lt;br /&gt;##&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;#&amp;amp;nbsp;  Some MIME-types for downloading Certificates and CRLs&lt;br /&gt;#&lt;br /&gt;AddType application/x-x509-ca-cert .crt&lt;br /&gt;AddType application/x-pkcs7-crl&amp;amp;nbsp; &amp;amp;nbsp; .crl&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Pass Phrase Dialog:&lt;br /&gt;#&amp;amp;nbsp;  Configure the pass phrase gathering process.&lt;br /&gt;#&amp;amp;nbsp;  The filtering dialog program (&amp;#96;builtin&amp;#39; is a internal&lt;br /&gt;#&amp;amp;nbsp;  terminal dialog) has to provide the pass phrase on stdout.&lt;br /&gt;SSLPassPhraseDialog&amp;amp;nbsp; builtin&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Inter-Process Session Cache:&lt;br /&gt;#&amp;amp;nbsp;  Configure the SSL Session Cache: First the mechanism &lt;br /&gt;#&amp;amp;nbsp;  to use and second the expiring timeout (in seconds).&lt;br /&gt;#SSLSessionCache&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; none&lt;br /&gt;#SSLSessionCache&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; shmht:logs/ssl_scache(512000)&lt;br /&gt;#SSLSessionCache&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; shmcb:logs/ssl_scache(512000)&lt;br /&gt;SSLSessionCache&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  dbm:logs/ssl-scache.log&lt;br /&gt;SSLSessionCacheTimeout&amp;amp;nbsp; 300&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Semaphore:&lt;br /&gt;#&amp;amp;nbsp;  Configure the path to the mutual exclusion semaphore the&lt;br /&gt;#&amp;amp;nbsp;  SSL engine uses internally for inter-process synchronization. &lt;br /&gt;#SSLMutex&amp;amp;nbsp; file:logs/ssl_mutex.log&lt;br /&gt;SSLMutex default&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Pseudo Random Number Generator (PRNG):&lt;br /&gt;#&amp;amp;nbsp;  Configure one or more sources to seed the PRNG of the &lt;br /&gt;#&amp;amp;nbsp;  SSL library. The seed data should be of good random quality.&lt;br /&gt;#&amp;amp;nbsp;  WARNING! On some platforms /dev/random blocks if not enough entropy&lt;br /&gt;#&amp;amp;nbsp;  is available. This means you then cannot use the /dev/random device&lt;br /&gt;#&amp;amp;nbsp;  because it would lead to very long connection times (as long as&lt;br /&gt;#&amp;amp;nbsp;  it requires to make more entropy available). But usually those&lt;br /&gt;#&amp;amp;nbsp;  platforms additionally provide a /dev/urandom device which doesn&amp;#39;t&lt;br /&gt;#&amp;amp;nbsp;  block. So, if available, use this one instead. Read the mod_ssl User&lt;br /&gt;#&amp;amp;nbsp;  Manual for more details.&lt;br /&gt;SSLRandomSeed startup builtin&lt;br /&gt;SSLRandomSeed connect builtin&lt;br /&gt;#SSLRandomSeed startup file:/dev/random&amp;amp;nbsp; 512&lt;br /&gt;#SSLRandomSeed startup file:/dev/urandom 512&lt;br /&gt;#SSLRandomSeed connect file:/dev/random&amp;amp;nbsp; 512&lt;br /&gt;#SSLRandomSeed connect file:/dev/urandom 512&lt;br /&gt;&lt;br /&gt;##&lt;br /&gt;## SSL Virtual Host Context&lt;br /&gt;##&lt;br /&gt;&lt;br /&gt;&amp;lt;VirtualHost _default_:443&amp;gt;&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp; General setup for the virtual host&lt;br /&gt;DocumentRoot &amp;quot;C:\Program Files\Apache Group\Apache2\htdocs_secure&amp;quot;&lt;br /&gt;ServerName localhost:443&lt;br /&gt;#ServerName www.my-domain.com:443&lt;br /&gt;ServerAdmin you@your.address&lt;br /&gt;ErrorLog logs/error.log&lt;br /&gt;TransferLog logs/access.log&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  SSL Engine Switch:&lt;br /&gt;#&amp;amp;nbsp;  Enable/Disable SSL for this virtual host.&lt;br /&gt;SSLEngine on&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  SSL Cipher Suite:&lt;br /&gt;#&amp;amp;nbsp;  List the ciphers that the client is permitted to negotiate.&lt;br /&gt;#&amp;amp;nbsp;  See the mod_ssl documentation for a complete list.&lt;br /&gt;SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Server Certificate:&lt;br /&gt;#&amp;amp;nbsp;  Point SSLCertificateFile at a PEM encoded certificate.&amp;amp;nbsp; If&lt;br /&gt;#&amp;amp;nbsp;  the certificate is encrypted, then you will be prompted for a&lt;br /&gt;#&amp;amp;nbsp;  pass phrase.&amp;amp;nbsp; Note that a kill -HUP will prompt again.&amp;amp;nbsp; Keep&lt;br /&gt;#&amp;amp;nbsp;  in mind that if you have both an RSA and a DSA certificate you&lt;br /&gt;#&amp;amp;nbsp;  can configure both in parallel (to also allow the use of DSA&lt;br /&gt;#&amp;amp;nbsp;  ciphers, etc.)&lt;br /&gt;SSLCertificateFile conf/ssl/my-server.cert&lt;br /&gt;#SSLCertificateFile conf/ssl.crt/server-dsa.crt&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Server Private Key:&lt;br /&gt;#&amp;amp;nbsp;  If the key is not combined with the certificate, use this&lt;br /&gt;#&amp;amp;nbsp;  directive to point at the key file.&amp;amp;nbsp; Keep in mind that if&lt;br /&gt;#&amp;amp;nbsp;  you&amp;#39;ve both a RSA and a DSA private key you can configure&lt;br /&gt;#&amp;amp;nbsp;  both in parallel (to also allow the use of DSA ciphers, etc.)&lt;br /&gt;SSLCertificateKeyFile conf/ssl/my-server.key&lt;br /&gt;#SSLCertificateKeyFile conf/ssl.key/server-dsa.key&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Server Certificate Chain:&lt;br /&gt;#&amp;amp;nbsp;  Point SSLCertificateChainFile at a file containing the&lt;br /&gt;#&amp;amp;nbsp;  concatenation of PEM encoded CA certificates which form the&lt;br /&gt;#&amp;amp;nbsp;  certificate chain for the server certificate. Alternatively&lt;br /&gt;#&amp;amp;nbsp;  the referenced file can be the same as SSLCertificateFile&lt;br /&gt;#&amp;amp;nbsp;  when the CA certificates are directly appended to the server&lt;br /&gt;#&amp;amp;nbsp;  certificate for convinience.&lt;br /&gt;#SSLCertificateChainFile conf/ssl.crt/ca.crt&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Certificate Authority (CA):&lt;br /&gt;#&amp;amp;nbsp;  Set the CA certificate verification path where to find CA&lt;br /&gt;#&amp;amp;nbsp;  certificates for client authentication or alternatively one&lt;br /&gt;#&amp;amp;nbsp;  huge file containing all of them (file must be PEM encoded)&lt;br /&gt;#&amp;amp;nbsp;  Note: Inside SSLCACertificatePath you need hash symlinks&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  to point to the certificate files. Use the provided&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  Makefile to update the hash symlinks after changes.&lt;br /&gt;#SSLCACertificatePath conf/ssl.crt&lt;br /&gt;#SSLCACertificateFile conf/ssl.crt/ca-bundle.crt&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Certificate Revocation Lists (CRL):&lt;br /&gt;#&amp;amp;nbsp;  Set the CA revocation path where to find CA CRLs for client&lt;br /&gt;#&amp;amp;nbsp;  authentication or alternatively one huge file containing all&lt;br /&gt;#&amp;amp;nbsp;  of them (file must be PEM encoded)&lt;br /&gt;#&amp;amp;nbsp;  Note: Inside SSLCARevocationPath you need hash symlinks&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  to point to the certificate files. Use the provided&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  Makefile to update the hash symlinks after changes.&lt;br /&gt;#SSLCARevocationPath conf/ssl.crl&lt;br /&gt;#SSLCARevocationFile conf/ssl.crl/ca-bundle.crl&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Client Authentication (Type):&lt;br /&gt;#&amp;amp;nbsp;  Client certificate verification type and depth.&amp;amp;nbsp; Types are&lt;br /&gt;#&amp;amp;nbsp;  none, optional, require and optional_no_ca.&amp;amp;nbsp; Depth is a&lt;br /&gt;#&amp;amp;nbsp;  number which specifies how deeply to verify the certificate&lt;br /&gt;#&amp;amp;nbsp;  issuer chain before deciding the certificate is not valid.&lt;br /&gt;#SSLVerifyClient require&lt;br /&gt;#SSLVerifyDepth&amp;amp;nbsp; 10&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Access Control:&lt;br /&gt;#&amp;amp;nbsp;  With SSLRequire you can do per-directory access control based&lt;br /&gt;#&amp;amp;nbsp;  on arbitrary complex boolean expressions containing server&lt;br /&gt;#&amp;amp;nbsp;  variable checks and other lookup directives.&amp;amp;nbsp; The syntax is a&lt;br /&gt;#&amp;amp;nbsp;  mixture between C and Perl.&amp;amp;nbsp; See the mod_ssl documentation&lt;br /&gt;#&amp;amp;nbsp;  for more details.&lt;br /&gt;#&amp;lt;Location&amp;gt;&lt;br /&gt;#SSLRequire (&amp;amp;nbsp; &amp;amp;nbsp; &amp;#37;{SSL_CIPHER} !&amp;#126; m/&amp;#94;(EXP&amp;#124;NULL)/ \&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; and &amp;#37;{SSL_CLIENT_S_DN_O} eq &amp;quot;Snake Oil, Ltd.&amp;quot; \&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; and &amp;#37;{SSL_CLIENT_S_DN_OU} in {&amp;quot;Staff&amp;quot;, &amp;quot;CA&amp;quot;, &amp;quot;Dev&amp;quot;} \&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; and &amp;#37;{TIME_WDAY} &amp;gt;= 1 and &amp;#37;{TIME_WDAY} &amp;lt;= 5 \&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; and &amp;#37;{TIME_HOUR} &amp;gt;= 8 and &amp;#37;{TIME_HOUR} &amp;lt;= 20&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  ) \&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  or &amp;#37;{REMOTE_ADDR} =&amp;#126; m/&amp;#94;192\.76\.162\.[0-9]+&amp;#36;/&lt;br /&gt;#&amp;lt;/Location&amp;gt;&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  SSL Engine Options:&lt;br /&gt;#&amp;amp;nbsp;  Set various options for the SSL engine.&lt;br /&gt;#&amp;amp;nbsp;  o FakeBasicAuth:&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  Translate the client X.509 into a Basic Authorisation.&amp;amp;nbsp; This means that&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  the standard Auth/DBMAuth methods can be used for access control.&amp;amp;nbsp; The&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  user name is the &amp;#96;one line&amp;#39; version of the client&amp;#39;s X.509 certificate.&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  Note that no password is obtained from the user. Every entry in the user&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  file needs this password: &amp;#96;xxj31ZMTZzkVA&amp;#39;.&lt;br /&gt;#&amp;amp;nbsp;  o ExportCertData:&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  This exports two additional environment variables: SSL_CLIENT_CERT and&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  SSL_SERVER_CERT. These contain the PEM-encoded certificates of the&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  server (always existing) and the client (only existing when client&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  authentication is used). This can be used to import the certificates&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  into CGI scripts.&lt;br /&gt;#&amp;amp;nbsp;  o StdEnvVars:&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  This exports the standard SSL/TLS related &amp;#96;SSL_&amp;#42;&amp;#39; environment variables.&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  Per default this exportation is switched off for performance reasons,&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  because the extraction step is an expensive operation and is usually&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  useless for serving static content. So one usually enables the&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  exportation for CGI and SSI requests only.&lt;br /&gt;#&amp;amp;nbsp;  o CompatEnvVars:&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  This exports obsolete environment variables for backward compatibility&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  to Apache-SSL 1.x, mod_ssl 2.0.x, Sioux 1.0 and Stronghold 2.x. Use this&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  to provide compatibility to existing CGI scripts.&lt;br /&gt;#&amp;amp;nbsp;  o StrictRequire:&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  This denies access when &amp;quot;SSLRequireSSL&amp;quot; or &amp;quot;SSLRequire&amp;quot; applied even&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  under a &amp;quot;Satisfy any&amp;quot; situation, i.e. when it applies access is denied&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  and no other module can change it.&lt;br /&gt;#&amp;amp;nbsp;  o OptRenegotiate:&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  This enables optimized SSL connection renegotiation handling when SSL&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  directives are used in per-directory context. &lt;br /&gt;#SSLOptions +FakeBasicAuth +ExportCertData +CompatEnvVars +StrictRequire&lt;br /&gt;&amp;lt;Files &amp;#126; &amp;quot;\.(cgi&amp;#124;shtml&amp;#124;phtml&amp;#124;php3?)&amp;#36;&amp;quot;&amp;gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; SSLOptions +StdEnvVars&lt;br /&gt;&amp;lt;/Files&amp;gt;&lt;br /&gt;&amp;lt;Directory &amp;quot;cgi-bin&amp;quot;&amp;gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; SSLOptions +StdEnvVars&lt;br /&gt;&amp;lt;/Directory&amp;gt;&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  SSL Protocol Adjustments:&lt;br /&gt;#&amp;amp;nbsp;  The safe and default but still SSL/TLS standard compliant shutdown&lt;br /&gt;#&amp;amp;nbsp;  approach is that mod_ssl sends the close notify alert but doesn&amp;#39;t wait for&lt;br /&gt;#&amp;amp;nbsp;  the close notify alert from client. When you need a different shutdown&lt;br /&gt;#&amp;amp;nbsp;  approach you can use one of the following variables:&lt;br /&gt;#&amp;amp;nbsp;  o ssl-unclean-shutdown:&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  This forces an unclean shutdown when the connection is closed, i.e. no&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  SSL close notify alert is send or allowed to received.&amp;amp;nbsp; This violates&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  the SSL/TLS standard but is needed for some brain-dead browsers. Use&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  this when you receive I/O errors because of the standard approach where&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  mod_ssl sends the close notify alert.&lt;br /&gt;#&amp;amp;nbsp;  o ssl-accurate-shutdown:&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  This forces an accurate shutdown when the connection is closed, i.e. a&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  SSL close notify alert is send and mod_ssl waits for the close notify&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  alert of the client. This is 100&amp;#37; SSL/TLS standard compliant, but in&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  practice often causes hanging connections with brain-dead browsers. Use&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  this only for browsers where you know that their SSL implementation&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  works correctly. &lt;br /&gt;#&amp;amp;nbsp;  Notice: Most problems of broken clients are also related to the HTTP&lt;br /&gt;#&amp;amp;nbsp;  keep-alive facility, so you usually additionally want to disable&lt;br /&gt;#&amp;amp;nbsp;  keep-alive for those clients, too. Use variable &amp;quot;nokeepalive&amp;quot; for this.&lt;br /&gt;#&amp;amp;nbsp;  Similarly, one has to force some clients to use HTTP/1.0 to workaround&lt;br /&gt;#&amp;amp;nbsp;  their broken HTTP/1.1 implementation. Use variables &amp;quot;downgrade-1.0&amp;quot; and&lt;br /&gt;#&amp;amp;nbsp;  &amp;quot;force-response-1.0&amp;quot; for this.&lt;br /&gt;SetEnvIf User-Agent &amp;quot;.&amp;#42;MSIE.&amp;#42;&amp;quot; \&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  nokeepalive ssl-unclean-shutdown \&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  downgrade-1.0 force-response-1.0&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp;  Per-Server Logging:&lt;br /&gt;#&amp;amp;nbsp;  The home of a custom SSL log file. Use this when you want a&lt;br /&gt;#&amp;amp;nbsp;  compact non-error SSL logfile on a virtual host basis.&lt;br /&gt;CustomLog logs/ssl_request_log \&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;&amp;#37;t &amp;#37;h &amp;#37;{SSL_PROTOCOL}x &amp;#37;{SSL_CIPHER}x \&amp;quot;&amp;#37;r\&amp;quot; &amp;#37;b&amp;quot;&lt;br /&gt;&lt;br /&gt;&amp;lt;/VirtualHost&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;&lt;br /&gt;#&amp;lt;/IfDefine&amp;gt;&amp;lt;/lj-cut&amp;gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&amp;lt;lj-cut text=&amp;quot;httpd.conf&amp;quot;&amp;gt;&lt;br /&gt;&amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt;HTTPD.CONF&amp;lt;/font&amp;gt; &lt;br /&gt;#&lt;br /&gt;# Based upon the NCSA server configuration files originally by Rob McCool.&lt;br /&gt;#&lt;br /&gt;# This is the main Apache server configuration file.&amp;amp;nbsp; It contains the&lt;br /&gt;# configuration directives that give the server its instructions.&lt;br /&gt;# See &amp;lt;URL:http://httpd.apache.org/docs/2.0/&amp;gt; for detailed information about&lt;br /&gt;# the directives.&lt;br /&gt;#&lt;br /&gt;# Do NOT simply read the instructions in here without understanding&lt;br /&gt;# what they do.&amp;amp;nbsp; They&amp;#39;re here only as hints or reminders.&amp;amp;nbsp; If you are unsure&lt;br /&gt;# consult the online docs. You have been warned.&amp;amp;nbsp; &lt;br /&gt;#&lt;br /&gt;# The configuration directives are grouped into three basic sections:&lt;br /&gt;#&amp;amp;nbsp; 1. Directives that control the operation of the Apache server process as a&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  whole (the &amp;#39;global environment&amp;#39;).&lt;br /&gt;#&amp;amp;nbsp; 2. Directives that define the parameters of the &amp;#39;main&amp;#39; or &amp;#39;default&amp;#39; server,&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  which responds to requests that aren&amp;#39;t handled by a virtual host.&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  These directives also provide default values for the settings&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  of all virtual hosts.&lt;br /&gt;#&amp;amp;nbsp; 3. Settings for virtual hosts, which allow Web requests to be sent to&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  different IP addresses or hostnames and have them handled by the&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp;  same Apache server process.&lt;br /&gt;#&lt;br /&gt;# Configuration and logfile names: If the filenames you specify for many&lt;br /&gt;# of the server&amp;#39;s control files begin with &amp;quot;/&amp;quot; (or &amp;quot;drive:/&amp;quot; for Win32), the&lt;br /&gt;# server will use that explicit path.&amp;amp;nbsp; If the filenames do &amp;#42;not&amp;#42; begin&lt;br /&gt;# with &amp;quot;/&amp;quot;, the value of ServerRoot is prepended -- so &amp;quot;logs/foo.log&amp;quot;&lt;br /&gt;# with ServerRoot set to &amp;quot;C:/Program Files/Apache Group/Apache2&amp;quot; will be interpreted by the&lt;br /&gt;# server as &amp;quot;C:/Program Files/Apache Group/Apache2/logs/foo.log&amp;quot;.&lt;br /&gt;#&lt;br /&gt;# NOTE: Where filenames are specified, you must use forward slashes&lt;br /&gt;# instead of backslashes (e.g., &amp;quot;c:/apache&amp;quot; instead of &amp;quot;c:\apache&amp;quot;).&lt;br /&gt;# If a drive letter is omitted, the drive on which Apache.exe is located&lt;br /&gt;# will be used by default.&amp;amp;nbsp; It is recommended that you always supply&lt;br /&gt;# an explicit drive letter in absolute paths, however, to avoid&lt;br /&gt;# confusion.&lt;br /&gt;#&lt;br /&gt;&lt;br /&gt;### Section 1: Global Environment&lt;br /&gt;#&lt;br /&gt;# The directives in this section affect the overall operation of Apache,&lt;br /&gt;# such as the number of concurrent requests it can handle or where it&lt;br /&gt;# can find its configuration files.&lt;br /&gt;#&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# ServerRoot: The top of the directory tree under which the server&amp;#39;s&lt;br /&gt;# configuration, error, and log files are kept.&lt;br /&gt;#&lt;br /&gt;# NOTE!&amp;amp;nbsp; If you intend to place this on an NFS (or otherwise network)&lt;br /&gt;# mounted filesystem then please read the LockFile documentation (available&lt;br /&gt;# at &amp;lt;URL:http://httpd.apache.org/docs/2.0/mod/mpm_common.html#lockfile&amp;gt;);&lt;br /&gt;# you will save yourself a lot of trouble.&lt;br /&gt;#&lt;br /&gt;# Do NOT add a slash at the end of the directory path.&lt;br /&gt;#&lt;br /&gt;ServerRoot &amp;quot;C:/Program Files/Apache Group/Apache2&amp;quot;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# ScoreBoardFile: File used to store internal server process information.&lt;br /&gt;# If unspecified (the default), the scoreboard will be stored in an&lt;br /&gt;# anonymous shared memory segment, and will be unavailable to third-party&lt;br /&gt;# applications.&lt;br /&gt;# If specified, ensure that no two invocations of Apache share the same&lt;br /&gt;# scoreboard file. The scoreboard file MUST BE STORED ON A LOCAL DISK.&lt;br /&gt;#&lt;br /&gt;#ScoreBoardFile logs/apache_runtime_status&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# PidFile: The file in which the server should record its process&lt;br /&gt;# identification number when it starts.&lt;br /&gt;#&lt;br /&gt;PidFile logs/httpd.pid&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Timeout: The number of seconds before receives and sends time out.&lt;br /&gt;#&lt;br /&gt;Timeout 300&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# KeepAlive: Whether or not to allow persistent connections (more than&lt;br /&gt;# one request per connection). Set to &amp;quot;Off&amp;quot; to deactivate.&lt;br /&gt;#&lt;br /&gt;KeepAlive On&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# MaxKeepAliveRequests: The maximum number of requests to allow&lt;br /&gt;# during a persistent connection. Set to 0 to allow an unlimited amount.&lt;br /&gt;# We recommend you leave this number high, for maximum performance.&lt;br /&gt;#&lt;br /&gt;MaxKeepAliveRequests 100&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# KeepAliveTimeout: Number of seconds to wait for the next request from the&lt;br /&gt;# same client on the same connection.&lt;br /&gt;#&lt;br /&gt;KeepAliveTimeout 15&lt;br /&gt;&lt;br /&gt;##&lt;br /&gt;## Server-Pool Size Regulation (MPM specific)&lt;br /&gt;## &lt;br /&gt;&lt;br /&gt;# WinNT MPM&lt;br /&gt;# ThreadsPerChild: constant number of worker threads in the server process&lt;br /&gt;# MaxRequestsPerChild: maximum&amp;amp;nbsp; number of requests a server process serves&lt;br /&gt;&amp;lt;IfModule mpm_winnt.c&amp;gt;&lt;br /&gt;ThreadsPerChild 250&lt;br /&gt;MaxRequestsPerChild&amp;amp;nbsp; 0&lt;br /&gt;&amp;lt;/IfModule&amp;gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Listen: Allows you to bind Apache to specific IP addresses and/or&lt;br /&gt;# ports, instead of the default. See also the &amp;lt;VirtualHost&amp;gt;&lt;br /&gt;# directive.&lt;br /&gt;#&lt;br /&gt;# Change this to Listen on specific IP addresses as shown below to &lt;br /&gt;# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)&lt;br /&gt;#&lt;br /&gt;#Listen 12.34.56.78:80&lt;br /&gt;Listen 80&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Dynamic Shared Object (DSO) Support&lt;br /&gt;#&lt;br /&gt;# To be able to use the functionality of a module which was built as a DSO you&lt;br /&gt;# have to place corresponding &amp;#96;LoadModule&amp;#39; lines at this location so the&lt;br /&gt;# directives contained in it are actually available _before_ they are used.&lt;br /&gt;# Statically compiled modules (those listed by &amp;#96;httpd -l&amp;#39;) do not need&lt;br /&gt;# to be loaded here.&lt;br /&gt;#&lt;br /&gt;# Example:&lt;br /&gt;# LoadModule foo_module modules/mod_foo.so&lt;br /&gt;#&lt;br /&gt;LoadModule access_module modules/mod_access.so&lt;br /&gt;LoadModule actions_module modules/mod_actions.so&lt;br /&gt;LoadModule alias_module modules/mod_alias.so&lt;br /&gt;LoadModule asis_module modules/mod_asis.so&lt;br /&gt;LoadModule auth_module modules/mod_auth.so&lt;br /&gt;#LoadModule auth_anon_module modules/mod_auth_anon.so&lt;br /&gt;#LoadModule auth_dbm_module modules/mod_auth_dbm.so&lt;br /&gt;#LoadModule auth_digest_module modules/mod_auth_digest.so&lt;br /&gt;LoadModule autoindex_module modules/mod_autoindex.so&lt;br /&gt;#LoadModule cern_meta_module modules/mod_cern_meta.so&lt;br /&gt;LoadModule cgi_module modules/mod_cgi.so&lt;br /&gt;#LoadModule dav_module modules/mod_dav.so&lt;br /&gt;#LoadModule dav_fs_module modules/mod_dav_fs.so&lt;br /&gt;LoadModule dir_module modules/mod_dir.so&lt;br /&gt;LoadModule env_module modules/mod_env.so&lt;br /&gt;#LoadModule expires_module modules/mod_expires.so&lt;br /&gt;#LoadModule file_cache_module modules/mod_file_cache.so&lt;br /&gt;#LoadModule headers_module modules/mod_headers.so&lt;br /&gt;LoadModule imap_module modules/mod_imap.so&lt;br /&gt;LoadModule include_module modules/mod_include.so&lt;br /&gt;#LoadModule info_module modules/mod_info.so&lt;br /&gt;LoadModule isapi_module modules/mod_isapi.so&lt;br /&gt;LoadModule log_config_module modules/mod_log_config.so&lt;br /&gt;LoadModule mime_module modules/mod_mime.so&lt;br /&gt;#LoadModule mime_magic_module modules/mod_mime_magic.so&lt;br /&gt;#LoadModule proxy_module modules/mod_proxy.so&lt;br /&gt;#LoadModule proxy_connect_module modules/mod_proxy_connect.so&lt;br /&gt;#LoadModule proxy_http_module modules/mod_proxy_http.so&lt;br /&gt;#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so&lt;br /&gt;LoadModule negotiation_module modules/mod_negotiation.so&lt;br /&gt;#LoadModule rewrite_module modules/mod_rewrite.so&lt;br /&gt;LoadModule setenvif_module modules/mod_setenvif.so&lt;br /&gt;#LoadModule speling_module modules/mod_speling.so&lt;br /&gt;#LoadModule status_module modules/mod_status.so&lt;br /&gt;#LoadModule unique_id_module modules/mod_unique_id.so&lt;br /&gt;LoadModule userdir_module modules/mod_userdir.so&lt;br /&gt;#LoadModule usertrack_module modules/mod_usertrack.so&lt;br /&gt;#LoadModule vhost_alias_module modules/mod_vhost_alias.so&lt;br /&gt;LoadModule ssl_module modules/mod_ssl.so&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# ExtendedStatus controls whether Apache will generate &amp;quot;full&amp;quot; status&lt;br /&gt;# information (ExtendedStatus On) or just basic information (ExtendedStatus&lt;br /&gt;# Off) when the &amp;quot;server-status&amp;quot; handler is called. The default is Off.&lt;br /&gt;#&lt;br /&gt;#ExtendedStatus On&lt;br /&gt;&lt;br /&gt;### Section 2: &amp;#39;Main&amp;#39; server configuration&lt;br /&gt;#&lt;br /&gt;# The directives in this section set up the values used by the &amp;#39;main&amp;#39;&lt;br /&gt;# server, which responds to any requests that aren&amp;#39;t handled by a&lt;br /&gt;# &amp;lt;VirtualHost&amp;gt; definition.&amp;amp;nbsp; These values also provide defaults for&lt;br /&gt;# any &amp;lt;VirtualHost&amp;gt; containers you may define later in the file.&lt;br /&gt;#&lt;br /&gt;# All of these directives may appear inside &amp;lt;VirtualHost&amp;gt; containers,&lt;br /&gt;# in which case these default settings will be overridden for the&lt;br /&gt;# virtual host being defined.&lt;br /&gt;#&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# ServerAdmin: Your address, where problems with the server should be&lt;br /&gt;# e-mailed.&amp;amp;nbsp; This address appears on some server-generated pages, such&lt;br /&gt;# as error documents.&amp;amp;nbsp; e.g. admin@your-domain.com&lt;br /&gt;#&lt;br /&gt;ServerAdmin test@test.com&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# ServerName gives the name and port that the server uses to identify itself.&lt;br /&gt;# This can often be determined automatically, but we recommend you specify&lt;br /&gt;# it explicitly to prevent problems during startup.&lt;br /&gt;#&lt;br /&gt;# If this is not set to valid DNS name for your host, server-generated&lt;br /&gt;# redirections will not work.&amp;amp;nbsp; See also the UseCanonicalName directive.&lt;br /&gt;#&lt;br /&gt;# If your host doesn&amp;#39;t have a registered DNS name, enter its IP address here.&lt;br /&gt;# You will have to access it by its address anyway, and this will make &lt;br /&gt;# redirections work in a sensible way.&lt;br /&gt;#&lt;br /&gt;ServerName localhost:80&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# UseCanonicalName: Determines how Apache constructs self-referencing &lt;br /&gt;# URLs and the SERVER_NAME and SERVER_PORT variables.&lt;br /&gt;# When set &amp;quot;Off&amp;quot;, Apache will use the Hostname and Port supplied&lt;br /&gt;# by the client.&amp;amp;nbsp; When set &amp;quot;On&amp;quot;, Apache will use the value of the&lt;br /&gt;# ServerName directive.&lt;br /&gt;#&lt;br /&gt;UseCanonicalName Off&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# DocumentRoot: The directory out of which you will serve your&lt;br /&gt;# documents. By default, all requests are taken from this directory, but&lt;br /&gt;# symbolic links and aliases may be used to point to other locations.&lt;br /&gt;#&lt;br /&gt;DocumentRoot &amp;quot;C:/Program Files/Apache Group/Apache2/htdocs&amp;quot;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Each directory to which Apache has access can be configured with respect&lt;br /&gt;# to which services and features are allowed and/or disabled in that&lt;br /&gt;# directory (and its subdirectories). &lt;br /&gt;#&lt;br /&gt;# First, we configure the &amp;quot;default&amp;quot; to be a very restrictive set of &lt;br /&gt;# features.&amp;amp;nbsp; &lt;br /&gt;#&lt;br /&gt;&amp;lt;Directory /&amp;gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Options FollowSymLinks&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; AllowOverride None&lt;br /&gt;&amp;lt;/Directory&amp;gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Note that from this point forward you must specifically allow&lt;br /&gt;# particular features to be enabled - so if something&amp;#39;s not working as&lt;br /&gt;# you might expect, make sure that you have specifically enabled it&lt;br /&gt;# below.&lt;br /&gt;#&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# This should be changed to whatever you set DocumentRoot to.&lt;br /&gt;#&lt;br /&gt;&amp;lt;Directory &amp;quot;C:/Program Files/Apache Group/Apache2/htdocs&amp;quot;&amp;gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Possible values for the Options directive are &amp;quot;None&amp;quot;, &amp;quot;All&amp;quot;,&lt;br /&gt;# or any combination of:&lt;br /&gt;#&amp;amp;nbsp;  Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews&lt;br /&gt;#&lt;br /&gt;# Note that &amp;quot;MultiViews&amp;quot; must be named &amp;#42;explicitly&amp;#42; --- &amp;quot;Options All&amp;quot;&lt;br /&gt;# doesn&amp;#39;t give it to you.&lt;br /&gt;#&lt;br /&gt;# The Options directive is both complicated and important.&amp;amp;nbsp; Please see&lt;br /&gt;# http://httpd.apache.org/docs/2.0/mod/core.html#options&lt;br /&gt;# for more information.&lt;br /&gt;#&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Options Indexes FollowSymLinks&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# AllowOverride controls what directives may be placed in .htaccess files.&lt;br /&gt;# It can be &amp;quot;All&amp;quot;, &amp;quot;None&amp;quot;, or any combination of the keywords:&lt;br /&gt;#&amp;amp;nbsp;  Options FileInfo AuthConfig Limit&lt;br /&gt;#&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; AllowOverride None&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Controls who can get stuff from this server.&lt;br /&gt;#&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Order allow,deny&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Allow from all&lt;br /&gt;&lt;br /&gt;&amp;lt;/Directory&amp;gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# UserDir: The name of the directory that is appended onto a user&amp;#39;s home&lt;br /&gt;# directory if a &amp;#126;user request is received.&amp;amp;nbsp; Be especially careful to use&lt;br /&gt;# proper, forward slashes here.&amp;amp;nbsp; On Windows NT, &amp;quot;Personal/My Website&amp;quot;&lt;br /&gt;# is a more appropriate choice.&lt;br /&gt;#&lt;br /&gt;UserDir &amp;quot;My Documents/My Website&amp;quot;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Control access to UserDir directories.&amp;amp;nbsp; The following is an example&lt;br /&gt;# for a site where these directories are restricted to read-only.&lt;br /&gt;#&lt;br /&gt;# You must correct the path for the root to match your system&amp;#39;s configured&lt;br /&gt;# user directory location, e.g. &amp;quot;C:/WinNT/profiles/&amp;#42;/My Documents/My Website&amp;quot;&lt;br /&gt;# or whichever, as appropriate.&lt;br /&gt;#&lt;br /&gt;#&amp;lt;Directory &amp;quot;C:/Documents and Settings/&amp;#42;/My Documents/My Website&amp;quot;&amp;gt;&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; AllowOverride FileInfo AuthConfig Limit&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;lt;Limit GET POST OPTIONS PROPFIND&amp;gt;&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; Order allow,deny&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; Allow from all&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;lt;/Limit&amp;gt;&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;lt;LimitExcept GET POST OPTIONS PROPFIND&amp;gt;&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; Order deny,allow&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; Deny from all&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;lt;/LimitExcept&amp;gt;&lt;br /&gt;#&amp;lt;/Directory&amp;gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# DirectoryIndex: sets the file that Apache will serve if a directory&lt;br /&gt;# is requested.&lt;br /&gt;#&lt;br /&gt;# The index.html.var file (a type-map) is used to deliver content-&lt;br /&gt;# negotiated documents.&amp;amp;nbsp; The MultiViews Option can be used for the &lt;br /&gt;# same purpose, but it is much slower.&lt;br /&gt;#&lt;br /&gt;DirectoryIndex index.html index.html.var&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# AccessFileName: The name of the file to look for in each directory&lt;br /&gt;# for additional configuration directives.&amp;amp;nbsp; See also the AllowOverride &lt;br /&gt;# directive.&lt;br /&gt;#&lt;br /&gt;AccessFileName .htaccess&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# The following lines prevent .htaccess and .htpasswd files from being &lt;br /&gt;# viewed by Web clients. &lt;br /&gt;#&lt;br /&gt;&amp;lt;FilesMatch &amp;quot;&amp;#94;\.ht&amp;quot;&amp;gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Order allow,deny&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Deny from all&lt;br /&gt;&amp;lt;/FilesMatch&amp;gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# TypesConfig describes where the mime.types file (or equivalent) is&lt;br /&gt;# to be found.&lt;br /&gt;#&lt;br /&gt;TypesConfig conf/mime.types&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# DefaultType is the default MIME type the server will use for a document&lt;br /&gt;# if it cannot otherwise determine one, such as from filename extensions.&lt;br /&gt;# If your server contains mostly text or HTML documents, &amp;quot;text/plain&amp;quot; is&lt;br /&gt;# a good value.&amp;amp;nbsp; If most of your content is binary, such as applications&lt;br /&gt;# or images, you may want to use &amp;quot;application/octet-stream&amp;quot; instead to&lt;br /&gt;# keep browsers from trying to display binary files as though they are&lt;br /&gt;# text.&lt;br /&gt;#&lt;br /&gt;DefaultType text/plain&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# The mod_mime_magic module allows the server to use various hints from the&lt;br /&gt;# contents of the file itself to determine its type.&amp;amp;nbsp; The MIMEMagicFile&lt;br /&gt;# directive tells the module where the hint definitions are located.&lt;br /&gt;#&lt;br /&gt;&amp;lt;IfModule mod_mime_magic.c&amp;gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; MIMEMagicFile conf/magic&lt;br /&gt;&amp;lt;/IfModule&amp;gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# HostnameLookups: Log the names of clients or just their IP addresses&lt;br /&gt;# e.g., www.apache.org (on) or 204.62.129.132 (off).&lt;br /&gt;# The default is off because it&amp;#39;d be overall better for the net if people&lt;br /&gt;# had to knowingly turn this feature on, since enabling it means that&lt;br /&gt;# each client request will result in AT LEAST one lookup request to the&lt;br /&gt;# nameserver.&lt;br /&gt;#&lt;br /&gt;HostnameLookups Off&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# EnableMMAP: Control whether memory-mapping is used to deliver&lt;br /&gt;# files (assuming that the underlying OS supports it).&lt;br /&gt;# The default is on; turn this off if you serve from NFS-mounted &lt;br /&gt;# filesystems.&amp;amp;nbsp; On some systems, turning it off (regardless of&lt;br /&gt;# filesystem) can improve performance; for details, please see&lt;br /&gt;# http://httpd.apache.org/docs/2.0/mod/core.html#enablemmap&lt;br /&gt;#&lt;br /&gt;#EnableMMAP off&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# EnableSendfile: Control whether the sendfile kernel support is &lt;br /&gt;# used&amp;amp;nbsp; to deliver files (assuming that the OS supports it).&lt;br /&gt;# The default is on; turn this off if you serve from NFS-mounted &lt;br /&gt;# filesystems.&amp;amp;nbsp; Please see&lt;br /&gt;# http://httpd.apache.org/docs/2.0/mod/core.html#enablesendfile&lt;br /&gt;#&lt;br /&gt;#EnableSendfile off&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# ErrorLog: The location of the error log file.&lt;br /&gt;# If you do not specify an ErrorLog directive within a &amp;lt;VirtualHost&amp;gt;&lt;br /&gt;# container, error messages relating to that virtual host will be&lt;br /&gt;# logged here.&amp;amp;nbsp; If you &amp;#42;do&amp;#42; define an error logfile for a &amp;lt;VirtualHost&amp;gt;&lt;br /&gt;# container, that host&amp;#39;s errors will be logged there and not here.&lt;br /&gt;#&lt;br /&gt;ErrorLog logs/error.log&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# LogLevel: Control the number of messages logged to the error.log.&lt;br /&gt;# Possible values include: debug, info, notice, warn, error, crit,&lt;br /&gt;# alert, emerg.&lt;br /&gt;#&lt;br /&gt;# LogLevel warn&lt;br /&gt;LogLevel debug&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# The following directives define some format nicknames for use with&lt;br /&gt;# a CustomLog directive (see below).&lt;br /&gt;#&lt;br /&gt;LogFormat &amp;quot;&amp;#37;h &amp;#37;l &amp;#37;u &amp;#37;t \&amp;quot;&amp;#37;r\&amp;quot; &amp;#37;&amp;gt;s &amp;#37;b \&amp;quot;&amp;#37;{Referer}i\&amp;quot; \&amp;quot;&amp;#37;{User-Agent}i\&amp;quot;&amp;quot; combined&lt;br /&gt;LogFormat &amp;quot;&amp;#37;h &amp;#37;l &amp;#37;u &amp;#37;t \&amp;quot;&amp;#37;r\&amp;quot; &amp;#37;&amp;gt;s &amp;#37;b&amp;quot; common&lt;br /&gt;LogFormat &amp;quot;&amp;#37;{Referer}i -&amp;gt; &amp;#37;U&amp;quot; referer&lt;br /&gt;LogFormat &amp;quot;&amp;#37;{User-agent}i&amp;quot; agent&lt;br /&gt;&lt;br /&gt;# You need to enable mod_logio.c to use &amp;#37;I and &amp;#37;O&lt;br /&gt;#LogFormat &amp;quot;&amp;#37;h &amp;#37;l &amp;#37;u &amp;#37;t \&amp;quot;&amp;#37;r\&amp;quot; &amp;#37;&amp;gt;s &amp;#37;b \&amp;quot;&amp;#37;{Referer}i\&amp;quot; \&amp;quot;&amp;#37;{User-Agent}i\&amp;quot; &amp;#37;I &amp;#37;O&amp;quot; combinedio&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# The location and format of the access logfile (Common Logfile Format).&lt;br /&gt;# If you do not define any access logfiles within a &amp;lt;VirtualHost&amp;gt;&lt;br /&gt;# container, they will be logged here.&amp;amp;nbsp; Contrariwise, if you &amp;#42;do&amp;#42;&lt;br /&gt;# define per-&amp;lt;VirtualHost&amp;gt; access logfiles, transactions will be&lt;br /&gt;# logged therein and &amp;#42;not&amp;#42; in this file.&lt;br /&gt;#&lt;br /&gt;CustomLog logs/access.log common&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# If you would like to have agent and referer logfiles, uncomment the&lt;br /&gt;# following directives.&lt;br /&gt;#&lt;br /&gt;#CustomLog logs/referer.log referer&lt;br /&gt;#CustomLog logs/agent.log agent&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# If you prefer a single logfile with access, agent, and referer information&lt;br /&gt;# (Combined Logfile Format) you can use the following directive.&lt;br /&gt;#&lt;br /&gt;#CustomLog logs/access.log combined&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# ServerTokens&lt;br /&gt;# This directive configures what you return as the Server HTTP response&lt;br /&gt;# Header. The default is &amp;#39;Full&amp;#39; which sends information about the OS-Type&lt;br /&gt;# and compiled in modules.&lt;br /&gt;# Set to one of:&amp;amp;nbsp; Full &amp;#124; OS &amp;#124; Minor &amp;#124; Minimal &amp;#124; Major &amp;#124; Prod&lt;br /&gt;# where Full conveys the most information, and Prod the least.&lt;br /&gt;#&lt;br /&gt;ServerTokens Full&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Optionally add a line containing the server version and virtual host&lt;br /&gt;# name to server-generated pages (internal error documents, FTP directory &lt;br /&gt;# listings, mod_status and mod_info output etc., but not CGI generated &lt;br /&gt;# documents or custom error documents).&lt;br /&gt;# Set to &amp;quot;EMail&amp;quot; to also include a mailto: link to the ServerAdmin.&lt;br /&gt;# Set to one of:&amp;amp;nbsp; On &amp;#124; Off &amp;#124; EMail&lt;br /&gt;#&lt;br /&gt;ServerSignature On&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Aliases: Add here as many aliases as you need (with no limit). The format is &lt;br /&gt;# Alias fakename realname&lt;br /&gt;#&lt;br /&gt;# Note that if you include a trailing / on fakename then the server will&lt;br /&gt;# require it to be present in the URL.&amp;amp;nbsp; So &amp;quot;/icons&amp;quot; isn&amp;#39;t aliased in this&lt;br /&gt;# example, only &amp;quot;/icons/&amp;quot;.&amp;amp;nbsp; If the fakename is slash-terminated, then the &lt;br /&gt;# realname must also be slash terminated, and if the fakename omits the &lt;br /&gt;# trailing slash, the realname must also omit it.&lt;br /&gt;#&lt;br /&gt;# We include the /icons/ alias for FancyIndexed directory listings.&amp;amp;nbsp; If you&lt;br /&gt;# do not use FancyIndexing, you may comment this out.&lt;br /&gt;#&lt;br /&gt;Alias /icons/ &amp;quot;C:/Program Files/Apache Group/Apache2/icons/&amp;quot;&lt;br /&gt;&lt;br /&gt;&amp;lt;Directory &amp;quot;C:/Program Files/Apache Group/Apache2/icons&amp;quot;&amp;gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Options Indexes MultiViews&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; AllowOverride None&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Order allow,deny&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Allow from all&lt;br /&gt;&amp;lt;/Directory&amp;gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# This should be changed to the ServerRoot/manual/.&amp;amp;nbsp; The alias provides&lt;br /&gt;# the manual, even if you choose to move your DocumentRoot.&amp;amp;nbsp; You may comment&lt;br /&gt;# this out if you do not care for the documentation.&lt;br /&gt;#&lt;br /&gt;AliasMatch &amp;#94;/manual(?:/(?:de&amp;#124;en&amp;#124;es&amp;#124;fr&amp;#124;ja&amp;#124;ko&amp;#124;ru))?(/.&amp;#42;)?&amp;#36; &amp;quot;C:/Program Files/Apache Group/Apache2/manual&amp;#36;1&amp;quot;&lt;br /&gt;&lt;br /&gt;&amp;lt;Directory &amp;quot;C:/Program Files/Apache Group/Apache2/manual&amp;quot;&amp;gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Options Indexes&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; AllowOverride None&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Order allow,deny&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Allow from all&lt;br /&gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;lt;Files &amp;#42;.html&amp;gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; SetHandler type-map&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;lt;/Files&amp;gt;&lt;br /&gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; SetEnvIf Request_URI &amp;#94;/manual/(de&amp;#124;en&amp;#124;es&amp;#124;fr&amp;#124;ja&amp;#124;ko&amp;#124;ru)/ prefer-language=&amp;#36;1&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; RedirectMatch 301 &amp;#94;/manual(?:/(de&amp;#124;en&amp;#124;es&amp;#124;fr&amp;#124;ja&amp;#124;ko&amp;#124;ru)){2,}(/.&amp;#42;)?&amp;#36; /manual/&amp;#36;1&amp;#36;2&lt;br /&gt;&amp;lt;/Directory&amp;gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# ScriptAlias: This controls which directories contain server scripts.&lt;br /&gt;# ScriptAliases are essentially the same as Aliases, except that&lt;br /&gt;# documents in the realname directory are treated as applications and&lt;br /&gt;# run by the server when requested rather than as documents sent to the client.&lt;br /&gt;# The same rules about trailing &amp;quot;/&amp;quot; apply to ScriptAlias directives as to&lt;br /&gt;# Alias.&lt;br /&gt;#&lt;br /&gt;ScriptAlias /cgi-bin/ &amp;quot;C:/Program Files/Apache Group/Apache2/cgi-bin/&amp;quot;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# &amp;quot;C:/Program Files/Apache Group/Apache2/cgi-bin&amp;quot; should be changed to whatever your ScriptAliased&lt;br /&gt;# CGI directory exists, if you have that configured.&lt;br /&gt;#&lt;br /&gt;&amp;lt;Directory &amp;quot;C:/Program Files/Apache Group/Apache2/cgi-bin&amp;quot;&amp;gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; AllowOverride None&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Options None&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Order allow,deny&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Allow from all&lt;br /&gt;&amp;lt;/Directory&amp;gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Redirect allows you to tell clients about documents which used to exist in&lt;br /&gt;# your server&amp;#39;s namespace, but do not anymore. This allows you to tell the&lt;br /&gt;# clients where to look for the relocated document.&lt;br /&gt;# Example:&lt;br /&gt;# Redirect permanent /foo http://www.example.com/bar&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Directives controlling the display of server-generated directory listings.&lt;br /&gt;#&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# IndexOptions: Controls the appearance of server-generated directory&lt;br /&gt;# listings.&lt;br /&gt;#&lt;br /&gt;IndexOptions FancyIndexing VersionSort&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# AddIcon&amp;#42; directives tell the server which icon to show for different&lt;br /&gt;# files or filename extensions.&amp;amp;nbsp; These are only displayed for&lt;br /&gt;# FancyIndexed directories.&lt;br /&gt;#&lt;br /&gt;AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip&lt;br /&gt;&lt;br /&gt;AddIconByType (TXT,/icons/text.gif) text/&amp;#42;&lt;br /&gt;AddIconByType (IMG,/icons/image2.gif) image/&amp;#42;&lt;br /&gt;AddIconByType (SND,/icons/sound2.gif) audio/&amp;#42;&lt;br /&gt;AddIconByType (VID,/icons/movie.gif) video/&amp;#42;&lt;br /&gt;&lt;br /&gt;AddIcon /icons/binary.gif .bin .exe&lt;br /&gt;AddIcon /icons/binhex.gif .hqx&lt;br /&gt;AddIcon /icons/tar.gif .tar&lt;br /&gt;AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv&lt;br /&gt;AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip&lt;br /&gt;AddIcon /icons/a.gif .ps .ai .eps&lt;br /&gt;AddIcon /icons/layout.gif .html .shtml .htm .pdf&lt;br /&gt;AddIcon /icons/text.gif .txt&lt;br /&gt;AddIcon /icons/c.gif .c&lt;br /&gt;AddIcon /icons/p.gif .pl .py&lt;br /&gt;AddIcon /icons/f.gif .for&lt;br /&gt;AddIcon /icons/dvi.gif .dvi&lt;br /&gt;AddIcon /icons/uuencoded.gif .uu&lt;br /&gt;AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl&lt;br /&gt;AddIcon /icons/tex.gif .tex&lt;br /&gt;AddIcon /icons/bomb.gif core&lt;br /&gt;&lt;br /&gt;AddIcon /icons/back.gif ..&lt;br /&gt;AddIcon /icons/hand.right.gif README&lt;br /&gt;AddIcon /icons/folder.gif &amp;#94;&amp;#94;DIRECTORY&amp;#94;&amp;#94;&lt;br /&gt;AddIcon /icons/blank.gif &amp;#94;&amp;#94;BLANKICON&amp;#94;&amp;#94;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# DefaultIcon is which icon to show for files which do not have an icon&lt;br /&gt;# explicitly set.&lt;br /&gt;#&lt;br /&gt;DefaultIcon /icons/unknown.gif&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# AddDescription allows you to place a short description after a file in&lt;br /&gt;# server-generated indexes.&amp;amp;nbsp; These are only displayed for FancyIndexed&lt;br /&gt;# directories.&lt;br /&gt;# Format: AddDescription &amp;quot;description&amp;quot; filename&lt;br /&gt;#&lt;br /&gt;#AddDescription &amp;quot;GZIP compressed document&amp;quot; .gz&lt;br /&gt;#AddDescription &amp;quot;tar archive&amp;quot; .tar&lt;br /&gt;#AddDescription &amp;quot;GZIP compressed tar archive&amp;quot; .tgz&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# ReadmeName is the name of the README file the server will look for by&lt;br /&gt;# default, and append to directory listings.&lt;br /&gt;#&lt;br /&gt;# HeaderName is the name of a file which should be prepended to&lt;br /&gt;# directory indexes. &lt;br /&gt;ReadmeName README.html&lt;br /&gt;HeaderName HEADER.html&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# IndexIgnore is a set of filenames which directory indexing should ignore&lt;br /&gt;# and not include in the listing.&amp;amp;nbsp; Shell-style wildcarding is permitted.&lt;br /&gt;#&lt;br /&gt;IndexIgnore .??&amp;#42; &amp;#42;&amp;#126; &amp;#42;# HEADER&amp;#42; README&amp;#42; RCS CVS &amp;#42;,v &amp;#42;,t&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# DefaultLanguage and AddLanguage allows you to specify the language of &lt;br /&gt;# a document. You can then use content negotiation to give a browser a &lt;br /&gt;# file in a language the user can understand.&lt;br /&gt;#&lt;br /&gt;# Specify a default language. This means that all data&lt;br /&gt;# going out without a specific language tag (see below) will &lt;br /&gt;# be marked with this one. You probably do NOT want to set&lt;br /&gt;# this unless you are sure it is correct for all cases.&lt;br /&gt;#&lt;br /&gt;# &amp;#42; It is generally better to not mark a page as &lt;br /&gt;# &amp;#42; being a certain language than marking it with the wrong&lt;br /&gt;# &amp;#42; language!&lt;br /&gt;#&lt;br /&gt;# DefaultLanguage nl&lt;br /&gt;#&lt;br /&gt;# Note 1: The suffix does not have to be the same as the language&lt;br /&gt;# keyword --- those with documents in Polish (whose net-standard&lt;br /&gt;# language code is pl) may wish to use &amp;quot;AddLanguage pl .po&amp;quot; to&lt;br /&gt;# avoid the ambiguity with the common suffix for perl scripts.&lt;br /&gt;#&lt;br /&gt;# Note 2: The example entries below illustrate that in some cases &lt;br /&gt;# the two character &amp;#39;Language&amp;#39; abbreviation is not identical to &lt;br /&gt;# the two character &amp;#39;Country&amp;#39; code for its country,&lt;br /&gt;# E.g. &amp;#39;Danmark/dk&amp;#39; versus &amp;#39;Danish/da&amp;#39;.&lt;br /&gt;#&lt;br /&gt;# Note 3: In the case of &amp;#39;ltz&amp;#39; we violate the RFC by using a three char&lt;br /&gt;# specifier. There is &amp;#39;work in progress&amp;#39; to fix this and get&lt;br /&gt;# the reference data for rfc1766 cleaned up.&lt;br /&gt;#&lt;br /&gt;# Catalan (ca) - Croatian (hr) - Czech (cs) - Danish (da) - Dutch (nl)&lt;br /&gt;# English (en) - Esperanto (eo) - Estonian (et) - French (fr) - German (de)&lt;br /&gt;# Greek-Modern (el) - Hebrew (he) - Italian (it) - Japanese (ja)&lt;br /&gt;# Korean (ko) - Luxembourgeois&amp;#42; (ltz) - Norwegian Nynorsk (nn)&lt;br /&gt;# Norwegian (no) - Polish (pl) - Portugese (pt)&lt;br /&gt;# Brazilian Portuguese (pt-BR) - Russian (ru) - Swedish (sv)&lt;br /&gt;# Simplified Chinese (zh-CN) - Spanish (es) - Traditional Chinese (zh-TW)&lt;br /&gt;#&lt;br /&gt;AddLanguage ca .ca&lt;br /&gt;AddLanguage cs .cz .cs&lt;br /&gt;AddLanguage da .dk&lt;br /&gt;AddLanguage de .de&lt;br /&gt;AddLanguage el .el&lt;br /&gt;AddLanguage en .en&lt;br /&gt;AddLanguage eo .eo&lt;br /&gt;AddLanguage es .es&lt;br /&gt;AddLanguage et .et&lt;br /&gt;AddLanguage fr .fr&lt;br /&gt;AddLanguage he .he&lt;br /&gt;AddLanguage hr .hr&lt;br /&gt;AddLanguage it .it&lt;br /&gt;AddLanguage ja .ja&lt;br /&gt;AddLanguage ko .ko&lt;br /&gt;AddLanguage ltz .ltz&lt;br /&gt;AddLanguage nl .nl&lt;br /&gt;AddLanguage nn .nn&lt;br /&gt;AddLanguage no .no&lt;br /&gt;AddLanguage pl .po&lt;br /&gt;AddLanguage pt .pt&lt;br /&gt;AddLanguage pt-BR .pt-br&lt;br /&gt;AddLanguage ru .ru&lt;br /&gt;AddLanguage sv .sv&lt;br /&gt;AddLanguage zh-CN .zh-cn&lt;br /&gt;AddLanguage zh-TW .zh-tw&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# LanguagePriority allows you to give precedence to some languages&lt;br /&gt;# in case of a tie during content negotiation.&lt;br /&gt;#&lt;br /&gt;# Just list the languages in decreasing order of preference. We have&lt;br /&gt;# more or less alphabetized them here. You probably want to change this.&lt;br /&gt;#&lt;br /&gt;LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# ForceLanguagePriority allows you to serve a result page rather than&lt;br /&gt;# MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)&lt;br /&gt;# [in case no accepted languages matched the available variants]&lt;br /&gt;#&lt;br /&gt;ForceLanguagePriority Prefer Fallback&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Commonly used filename extensions to character sets. You probably&lt;br /&gt;# want to avoid clashes with the language extensions, unless you&lt;br /&gt;# are good at carefully testing your setup after each change.&lt;br /&gt;# See http://www.iana.org/assignments/character-sets for the&lt;br /&gt;# official list of charset names and their respective RFCs.&lt;br /&gt;#&lt;br /&gt;AddCharset ISO-8859-1&amp;amp;nbsp; .iso8859-1 .latin1&lt;br /&gt;AddCharset ISO-8859-2&amp;amp;nbsp; .iso8859-2 .latin2 .cen&lt;br /&gt;AddCharset ISO-8859-3&amp;amp;nbsp; .iso8859-3 .latin3&lt;br /&gt;AddCharset ISO-8859-4&amp;amp;nbsp; .iso8859-4 .latin4&lt;br /&gt;AddCharset ISO-8859-5&amp;amp;nbsp; .iso8859-5 .latin5 .cyr .iso-ru&lt;br /&gt;AddCharset ISO-8859-6&amp;amp;nbsp; .iso8859-6 .latin6 .arb&lt;br /&gt;AddCharset ISO-8859-7&amp;amp;nbsp; .iso8859-7 .latin7 .grk&lt;br /&gt;AddCharset ISO-8859-8&amp;amp;nbsp; .iso8859-8 .latin8 .heb&lt;br /&gt;AddCharset ISO-8859-9&amp;amp;nbsp; .iso8859-9 .latin9 .trk&lt;br /&gt;AddCharset ISO-2022-JP .iso2022-jp .jis&lt;br /&gt;AddCharset ISO-2022-KR .iso2022-kr .kis&lt;br /&gt;AddCharset ISO-2022-CN .iso2022-cn .cis&lt;br /&gt;AddCharset Big5&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; .Big5&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  .big5&lt;br /&gt;# For russian, more than one charset is used (depends on client, mostly):&lt;br /&gt;AddCharset WINDOWS-1251 .cp-1251&amp;amp;nbsp;  .win-1251&lt;br /&gt;AddCharset CP866&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  .cp866&lt;br /&gt;AddCharset KOI8-r&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; .koi8-r .koi8-ru&lt;br /&gt;AddCharset KOI8-ru&amp;amp;nbsp; &amp;amp;nbsp;  .koi8-uk .ua&lt;br /&gt;AddCharset ISO-10646-UCS-2 .ucs2&lt;br /&gt;AddCharset ISO-10646-UCS-4 .ucs4&lt;br /&gt;AddCharset UTF-8&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  .utf8&lt;br /&gt;&lt;br /&gt;# The set below does not map to a specific (iso) standard&lt;br /&gt;# but works on a fairly wide range of browsers. Note that&lt;br /&gt;# capitalization actually matters (it should not, but it&lt;br /&gt;# does for some browsers).&lt;br /&gt;#&lt;br /&gt;# See http://www.iana.org/assignments/character-sets&lt;br /&gt;# for a list of sorts. But browsers support few.&lt;br /&gt;#&lt;br /&gt;AddCharset GB2312&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; .gb2312 .gb &lt;br /&gt;AddCharset utf-7&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  .utf7&lt;br /&gt;AddCharset utf-8&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;  .utf8&lt;br /&gt;AddCharset big5&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; .big5 .b5&lt;br /&gt;AddCharset EUC-TW&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; .euc-tw&lt;br /&gt;AddCharset EUC-JP&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; .euc-jp&lt;br /&gt;AddCharset EUC-KR&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; .euc-kr&lt;br /&gt;AddCharset shift_jis&amp;amp;nbsp;  .sjis&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# AddType allows you to add to or override the MIME configuration&lt;br /&gt;# file mime.types for specific file types.&lt;br /&gt;#&lt;br /&gt;#AddType application/x-tar .tgz&lt;br /&gt;#&lt;br /&gt;# AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress&lt;br /&gt;# information on the fly. Note: Not all browsers support this.&lt;br /&gt;# Despite the name similarity, the following Add&amp;#42; directives have nothing&lt;br /&gt;# to do with the FancyIndexing customization directives above.&lt;br /&gt;#&lt;br /&gt;#AddEncoding x-compress .Z&lt;br /&gt;#AddEncoding x-gzip .gz .tgz&lt;br /&gt;#&lt;br /&gt;# If the AddEncoding directives above are commented-out, then you&lt;br /&gt;# probably should define those extensions to indicate media types:&lt;br /&gt;#&lt;br /&gt;AddType application/x-compress .Z&lt;br /&gt;AddType application/x-gzip .gz .tgz&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# AddHandler allows you to map certain file extensions to &amp;quot;handlers&amp;quot;:&lt;br /&gt;# actions unrelated to filetype. These can be either built into the server&lt;br /&gt;# or added with the Action directive (see below)&lt;br /&gt;#&lt;br /&gt;# To use CGI scripts outside of ScriptAliased directories:&lt;br /&gt;# (You will also need to add &amp;quot;ExecCGI&amp;quot; to the &amp;quot;Options&amp;quot; directive.)&lt;br /&gt;#&lt;br /&gt;#AddHandler cgi-script .cgi&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# For files that include their own HTTP headers:&lt;br /&gt;#&lt;br /&gt;#AddHandler send-as-is asis&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# For server-parsed imagemap files:&lt;br /&gt;#&lt;br /&gt;#AddHandler imap-file map&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# For type maps (negotiated resources):&lt;br /&gt;# (This is enabled by default to allow the Apache &amp;quot;It Worked&amp;quot; page&lt;br /&gt;#&amp;amp;nbsp; to be distributed in multiple languages.)&lt;br /&gt;#&lt;br /&gt;AddHandler type-map var&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Filters allow you to process content before it is sent to the client.&lt;br /&gt;#&lt;br /&gt;# To parse .shtml files for server-side includes (SSI):&lt;br /&gt;# (You will also need to add &amp;quot;Includes&amp;quot; to the &amp;quot;Options&amp;quot; directive.)&lt;br /&gt;#&lt;br /&gt;#AddType text/html .shtml&lt;br /&gt;#AddOutputFilter INCLUDES .shtml&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Action lets you define media types that will execute a script whenever&lt;br /&gt;# a matching file is called. This eliminates the need for repeated URL&lt;br /&gt;# pathnames for oft-used CGI file processors.&lt;br /&gt;# Format: Action media/type /cgi-script/location&lt;br /&gt;# Format: Action handler-name /cgi-script/location&lt;br /&gt;#&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Customizable error responses come in three flavors:&lt;br /&gt;# 1) plain text 2) local redirects 3) external redirects&lt;br /&gt;#&lt;br /&gt;# Some examples:&lt;br /&gt;#ErrorDocument 500 &amp;quot;The server made a boo boo.&amp;quot;&lt;br /&gt;#ErrorDocument 404 /missing.html&lt;br /&gt;#ErrorDocument 404 &amp;quot;/cgi-bin/missing_handler.pl&amp;quot;&lt;br /&gt;#ErrorDocument 402 http://www.example.com/subscription_info.html&lt;br /&gt;#&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Putting this all together, we can internationalize error responses.&lt;br /&gt;#&lt;br /&gt;# We use Alias to redirect any /error/HTTP_&amp;lt;error&amp;gt;.html.var response to&lt;br /&gt;# our collection of by-error message multi-language collections.&amp;amp;nbsp; We use &lt;br /&gt;# includes to substitute the appropriate text.&lt;br /&gt;#&lt;br /&gt;# You can modify the messages&amp;#39; appearance without changing any of the&lt;br /&gt;# default HTTP_&amp;lt;error&amp;gt;.html.var files by adding the line:&lt;br /&gt;#&lt;br /&gt;#&amp;amp;nbsp;  Alias /error/include/ &amp;quot;/your/include/path/&amp;quot;&lt;br /&gt;#&lt;br /&gt;# which allows you to create your own set of files by starting with the&lt;br /&gt;# @exp_errordir@/include/ files and copying them to /your/include/path/, &lt;br /&gt;# even on a per-VirtualHost basis.&amp;amp;nbsp; The default include files will display&lt;br /&gt;# your Apache version number and your ServerAdmin email address regardless&lt;br /&gt;# of the setting of ServerSignature.&lt;br /&gt;#&lt;br /&gt;# The internationalized error documents require mod_alias, mod_include&lt;br /&gt;# and mod_negotiation.&amp;amp;nbsp; To activate them, uncomment the following 30 lines.&lt;br /&gt;&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; Alias /error/ &amp;quot;@exp_errordir@/&amp;quot;&lt;br /&gt;#&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;lt;Directory &amp;quot;@exp_errordir@&amp;quot;&amp;gt;&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; AllowOverride None&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; Options IncludesNoExec&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; AddOutputFilter Includes html&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; AddHandler type-map var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; Order allow,deny&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; Allow from all&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; LanguagePriority en cs de es fr it ja ko nl pl pt-br ro sv tr&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; ForceLanguagePriority Prefer Fallback&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; &amp;lt;/Directory&amp;gt;&lt;br /&gt;#&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 410 /error/HTTP_GONE.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# The following directives modify normal HTTP response behavior to&lt;br /&gt;# handle known problems with browser implementations.&lt;br /&gt;#&lt;br /&gt;BrowserMatch &amp;quot;Mozilla/2&amp;quot; nokeepalive&lt;br /&gt;BrowserMatch &amp;quot;MSIE 4\.0b2;&amp;quot; nokeepalive downgrade-1.0 force-response-1.0&lt;br /&gt;BrowserMatch &amp;quot;RealPlayer 4\.0&amp;quot; force-response-1.0&lt;br /&gt;BrowserMatch &amp;quot;Java/1\.0&amp;quot; force-response-1.0&lt;br /&gt;BrowserMatch &amp;quot;JDK/1\.0&amp;quot; force-response-1.0&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# The following directive disables redirects on non-GET requests for&lt;br /&gt;# a directory that does not include the trailing slash.&amp;amp;nbsp; This fixes a &lt;br /&gt;# problem with Microsoft WebFolders which does not appropriately handle &lt;br /&gt;# redirects for folders with DAV methods.&lt;br /&gt;# Same deal with Apple&amp;#39;s DAV filesystem and Gnome VFS support for DAV.&lt;br /&gt;#&lt;br /&gt;BrowserMatch &amp;quot;Microsoft Data Access Internet Publishing Provider&amp;quot; redirect-carefully&lt;br /&gt;BrowserMatch &amp;quot;MS FrontPage&amp;quot; redirect-carefully&lt;br /&gt;BrowserMatch &amp;quot;&amp;#94;WebDrive&amp;quot; redirect-carefully&lt;br /&gt;BrowserMatch &amp;quot;&amp;#94;WebDAVFS/1.[0123]&amp;quot; redirect-carefully&lt;br /&gt;BrowserMatch &amp;quot;&amp;#94;gnome-vfs&amp;quot; redirect-carefully&lt;br /&gt;BrowserMatch &amp;quot;&amp;#94;XML Spy&amp;quot; redirect-carefully&lt;br /&gt;BrowserMatch &amp;quot;&amp;#94;Dreamweaver-WebDAV-SCM1&amp;quot; redirect-carefully&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Allow server status reports generated by mod_status,&lt;br /&gt;# with the URL of http://servername/server-status&lt;br /&gt;# Change the &amp;quot;.localhost&amp;quot; to match your domain to enable.&lt;br /&gt;#&lt;br /&gt;#&amp;lt;Location /server-status&amp;gt;&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; SetHandler server-status&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; Order deny,allow&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; Deny from all&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; Allow from .localhost&lt;br /&gt;#&amp;lt;/Location&amp;gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Allow remote server configuration reports, with the URL of&lt;br /&gt;#&amp;amp;nbsp; http://servername/server-info (requires that mod_info.c be loaded).&lt;br /&gt;# Change the &amp;quot;.localhost&amp;quot; to match your domain to enable.&lt;br /&gt;#&lt;br /&gt;#&amp;lt;Location /server-info&amp;gt;&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; SetHandler server-info&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; Order deny,allow&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; Deny from all&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; Allow from .localhost&lt;br /&gt;#&amp;lt;/Location&amp;gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Bring in additional module-specific configurations&lt;br /&gt;#&lt;br /&gt;&amp;lt;IfModule mod_ssl.c&amp;gt;&lt;br /&gt;&amp;amp;nbsp; &amp;amp;nbsp; Include conf/ssl.conf&lt;br /&gt;&amp;lt;/IfModule&amp;gt;&lt;br /&gt;&lt;br /&gt;SSLMutex default&lt;br /&gt;SSLRandomSeed startup builtin&lt;br /&gt;SSLSessionCache none&lt;br /&gt;&lt;br /&gt;### Section 3: Virtual Hosts&lt;br /&gt;#&lt;br /&gt;# VirtualHost: If you want to maintain multiple domains/hostnames on your&lt;br /&gt;# machine you can setup VirtualHost containers for them. Most configurations&lt;br /&gt;# use only name-based virtual hosts so the server doesn&amp;#39;t need to worry about&lt;br /&gt;# IP addresses. This is indicated by the asterisks in the directives below.&lt;br /&gt;#&lt;br /&gt;# Please see the documentation at &lt;br /&gt;# &amp;lt;URL:http://httpd.apache.org/docs/2.0/vhosts/&amp;gt;&lt;br /&gt;# for further details before you try to setup virtual hosts.&lt;br /&gt;#&lt;br /&gt;# You may use the command line option &amp;#39;-S&amp;#39; to verify your virtual host&lt;br /&gt;# configuration.&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# Use name-based virtual hosting.&lt;br /&gt;#&lt;br /&gt;#NameVirtualHost &amp;#42;:80&lt;br /&gt;&lt;br /&gt;#&lt;br /&gt;# VirtualHost example:&lt;br /&gt;# Almost any Apache directive may go into a VirtualHost container.&lt;br /&gt;# The first VirtualHost section is used for requests without a known&lt;br /&gt;# server name.&lt;br /&gt;#&lt;br /&gt;#&amp;lt;VirtualHost &amp;#42;:80&amp;gt;&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ServerAdmin webmaster@dummy-host.example.com&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; DocumentRoot /www/docs/dummy-host.example.com&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ServerName dummy-host.example.com&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; ErrorLog logs/dummy-host.example.com-error_log&lt;br /&gt;#&amp;amp;nbsp; &amp;amp;nbsp; CustomLog logs/dummy-host.example.com-access_log common&lt;br /&gt;#&amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&amp;lt;VirtualHost localhost:443&amp;gt;&lt;br /&gt;SSLEngine On&lt;br /&gt;SSLCertificateFile conf/ssl/my-server.cert&lt;br /&gt;SSLCertificateKeyFile conf/ssl/my-server.key&lt;br /&gt;&amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;&amp;lt;/lj-cut&amp;gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;EDITED: &lt;br /&gt;&lt;br /&gt;Okay I found the problem.  &lt;br /&gt;&lt;br /&gt;In my original ssl.conf file the VirtualHost opening was:&lt;br /&gt;&lt;br /&gt;[VirtualHost _default_:443]&lt;br /&gt;&lt;br /&gt;I changed that to &lt;br /&gt;&lt;br /&gt;[VirtualHost localhost:443]&lt;br /&gt;&lt;br /&gt;Restarted apache2 and viola, my ssl docs are being served properly!&lt;br /&gt;&lt;br /&gt;:o)&lt;/div&gt;&lt;/div&gt;</description>
  <comments>https://apache.livejournal.com/35519.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>pkbarbiedoll</lj:poster>
  <lj:posterid>697617</lj:posterid>
  <lj:reply-count>2</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/35247.html</guid>
  <pubDate>Mon, 13 Nov 2006 10:36:26 GMT</pubDate>
  <title>php не интерпретируется</title>
  <author>sergejru</author>
  <link>https://apache.livejournal.com/35247.html</link>
  <description>Настраиваю сервер Apache под Gentoo Linux. Поставил вручную php (emerge не сработало). На сервере команды типа php [file] выполняются, а вот в браузере нет.&lt;br /&gt;Пытался прописывать AddType и Action, тогда говорит, что&lt;br /&gt;The requested URL /usr/local/bin/php/index.php was not found on this server.&lt;br /&gt;&lt;br /&gt;Интерпретатор здесь /usr/local/bin/php</description>
  <comments>https://apache.livejournal.com/35247.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>sergejru</lj:poster>
  <lj:posterid>8881275</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://apache.livejournal.com/34585.html</guid>
  <pubDate>Thu, 12 Oct 2006 21:17:19 GMT</pubDate>
  <title>Delegating authentication and authorization to the server host</title>
  <author>en_ki</author>
  <link>https://apache.livejournal.com/34585.html</link>
  <description>Suppose I am running an Apache server with SSL, and I want to delegate authentication and authorization to the host OS in the following fashion:&lt;br /&gt;&lt;br /&gt;(1) First, try to access the requested file as the default user (e.g., www-data).&lt;br /&gt;&lt;br /&gt;(2) If that doesn&apos;t work, use PAM to authenticate, and then setuid to the appropriate user, setgid to the appropriate group, and try to access the requested file that way.&lt;br /&gt;&lt;br /&gt;From the documentation it appears that the parts exist (suExec and mod_auth_pam), but it looks impossible to do the whole (short of writing my own module, of course), and my attempts at Googling didn&apos;t turn up anything useful.&lt;br /&gt;&lt;br /&gt;Does anyone know whether this can be done with existing tools, and if so how?  (Or if not, whether anyone is already working on such a project and would like some help?)</description>
  <comments>https://apache.livejournal.com/34585.html?view=comments#comments</comments>
  <lj:security>public</lj:security>
  <lj:poster>en_ki</lj:poster>
  <lj:posterid>597591</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
</channel>
</rss>
