bugdb. According to Ralf there are no plans to fix it and this doc is
pretty out of date anyways. See also PR#18574.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@101439
13f79535-47bb-0310-9956-
ffa450edef68
modssl-users mailing list. Perhaps your problem popped up at least once for
another user, too.
</dd>
- <dt>Problem Reports in the Bug Database <a href="http://www.modssl.org/support/bugdb/">http://www.modssl.org/support/bugdb/</a></dt>
- <dd>Third look inside the mod_ssl Bug Database. Perhaps
- someone else already has reported the problem.
- </dd>
-
</dl>
modssl-users mailing list. Perhaps your problem popped up at least once for
another user, too.
</dd>
- <dt>Problem Reports in the Bug Database <a
- href="http://www.modssl.org/support/bugdb/"
- >http://www.modssl.org/support/bugdb/</a></dt>
- <dd>Third look inside the mod_ssl Bug Database. Perhaps
- someone else already has reported the problem.
- </dd>
-
</dl>
</section>
</div>
<p>The above configuration is what you will want to use in almost
- all name-based virtual hosting situations. The only think that this
+ all name-based virtual hosting situations. The only thing that this
configuration will not work for, in fact, is when you are serving
different content based on differing IP addresses or ports.</p>
</note>
<p>The above configuration is what you will want to use in almost
- all name-based virtual hosting situations. The only think that this
+ all name-based virtual hosting situations. The only thing that this
configuration will not work for, in fact, is when you are serving
different content based on differing IP addresses or ports.</p>