| Apache Compile HOWTO | ||
|---|---|---|
| Prev | ||
10. Questions and Answers
- 1. FAQ
- 10.1.1. Is there such a HOWTO for Apache 2.0?
- 10.1.2. Why you don't add a description howto compile and setup mod_xyz?
- 10.1.3. If my clients are connecting to https://myserver.org an errormessage similar to this appears "Certificate not valid"
- 10.1.4. When I request a php file, the browser want to download it. Whats wrong?
- 10.1.5. Does this HOWTO also work on other platforms?
1. FAQ
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 <luc at delouw dot ch>
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.
10.1.3. If my clients are connecting to https://myserver.org an errormessage similar to this appears "Certificate not valid"
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 http://www.verisign.com. Such a certificate cost approx. 300 USD a year, depending on the strength of the key (56 or 128 Bits)
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 Section 6.3