old-www/HOWTO/Apache-Compile-HOWTO/faq.html

300 lines
5.3 KiB
HTML

<HTML
><HEAD
><TITLE
>Questions and Answers</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="Apache Compile HOWTO"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Further Information"
HREF="moreinfo.html"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Apache Compile HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="moreinfo.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
>&nbsp;</TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="FAQ"
></A
>10. Questions and Answers</H1
><DIV
CLASS="QANDASET"
><DL
><DT
>1. <A
HREF="faq.html#AEN1095"
>FAQ</A
></DT
><DD
><DL
><DT
>10.1.1. <A
HREF="faq.html#AEN1098"
>Is there such a HOWTO for Apache 2.0?</A
></DT
><DT
>10.1.2. <A
HREF="faq.html#AEN1104"
>Why you don't add a description howto compile and setup mod_xyz?</A
></DT
><DT
>10.1.3. <A
HREF="faq.html#AEN1109"
> If my clients are connecting to https://myserver.org an errormessage similar to this appears "Certificate not valid"
</A
></DT
><DT
>10.1.4. <A
HREF="faq.html#AEN1115"
> When I request a php file, the browser want to download it. Whats wrong?</A
></DT
><DT
>10.1.5. <A
HREF="faq.html#AEN1121"
> Does this HOWTO also work on other platforms?
</A
></DT
></DL
></DD
></DL
><DIV
CLASS="QANDADIV"
><H3
><A
NAME="AEN1095"
></A
>1. FAQ</H3
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1098"
></A
><B
>10.1.1. </B
>Is there such a HOWTO for Apache 2.0?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
> Not yet. The reason is that PHP 4.2.1 supports the Apache 2.0 API only experimentally and the speed of PHP is very poor
with Apache 2.0. As the new Apache brings lots of new features and massive speed improvements,
I will write such a HOWTO as soon as the PHP support is stable and more performant. I'm collecting now
Ideas and wishes from users what they like to see in a Apache 2.0 HOWTO. Feel free to write an email to
<TT
CLASS="EMAIL"
>&#60;<A
HREF="mailto:luc at delouw dot ch"
>luc at delouw dot ch</A
>&#62;</TT
>
</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1104"
></A
><B
>10.1.2. </B
>Why you don't add a description howto compile and setup mod_xyz?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>Because nobody requested it yet and I either did not know about a mod_xyz, or I did not found it useful. Feel free
to write me some suggestions what to add to the HOWTO. If there is more than one request, and it makes sense, it will maybe
added in further releases.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1109"
></A
><B
>10.1.3. </B
> If my clients are connecting to https://myserver.org an errormessage similar to this appears "Certificate not valid"
</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
> A: The certificate produced like described in this HOWTO is just a self-signed certificate. This means the CA (Certification Authority) is you. Your CA is not recognized as a valid CA by your users browser. You can either install the certificate on your users machines (Makes sense in small Intranet environments) or buy a certificate from a CA that is recognized by all major browsers. An example of such a CA is Verisign <A
HREF="http://www.verisign.com"
TARGET="_top"
>http://www.verisign.com</A
>. Such a certificate cost approx. 300 USD a year, depending on the strength of the key (56 or 128 Bits)</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1115"
></A
><B
>10.1.4. </B
> When I request a php file, the browser want to download it. Whats wrong?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
> You forgot to tell Apache what to do with the php files. So the php files are not processed by the php engine.
To do so, add the application type like described in <A
HREF="php.html#BUILD-PHP"
>Section 6.3</A
>
</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1121"
></A
><B
>10.1.5. </B
> Does this HOWTO also work on other platforms?
</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
> Not sure, Solaris should work, AIX and HP-UX do not. I did not got the time to try FreeBSD yet. My goal is to provide
a version of the HOWTO for all major Un*x platforms.
</P
></DIV
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="moreinfo.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>&nbsp;</TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Further Information</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>&nbsp;</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>