Differences between Apache 1.3 family vs. 2.0 family
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Differences between Apache 1.3 family vs. 2.0 family
Hi all
Can somebody tell me, what is the differences between Apache 1.3 family vs. 2.0 family? I've seen that both version are available at apache website, but I don't know which one is better for my job. I need Apache uses mod_rewrite, basic authentication via browser, also supports PHP 5+. I have downloaded the latest 2.0 family version, but after compiling it, looks like that it doesn't support mod_rewrite. Does downgrading to 1.3 family solve my problem? Does 1.3 support PHP 5+, basic authentication, and mod_rewrite? What is the differences between Apache 1.3 family vs. 2.0 family?
I can't see mod_rewrite.so file in /usr/local/apache/modules. But I use Apache 1.3, and I find the file in /usr/local/apacheold/libexec.
By the way, I am using Open SUSE 10.2, and my configure command for Apache 2 is : ./configure --prefix=/usr/local/apache --enable-module=so --enable-module=rewrite --enable-module=proxy --enable-shared=rewrite
I think it's just a syntax difference for the configure command. For Apache 2.0, running ./configure --help lists --enable-modules=MODULE-LIST as one of the options (not --enable-module=MODULE-LIST as you have listed). However, re-write also gets its own configure option, so I use the following:
Hi Steve
Thank you for your help, but unfortunately it still doesn't work. I can't find mod_rewrite.so under modules directory, also there is not any entry for mod_rewrite in httpd.conf file.
I don't have a mod_write.so in my modules directory either, but I have the following in my virtual hosts entries:
Code:
RewriteEngine on
RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)
RewriteRule .* - [F]
It disables the trace method - when I comment it out, tracing works, when it's not commented out, tracing is denied. So it seems that the functionality is built in somewhere else, but it works as long as --enable-rewrite is selected when configuring.
P.S. The preferred way to disable tracing is with TraceEnable - that's an old piece of code I've shown
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.