Hello, I have install latest Drupal, I come across with a problem: If I move the content of .htaccess into httpd.conf, the site is not accessible and error "HTTP 400 - BAD REQUEST" will be give out. If I leave the drupal config as in .htaccess, it is okay. However, I don't want to use .htacess in my production server, so anyone had experience in moving configurations to httpd.conf? (I am using Apache 2.2) Thanks.
On Jul 25, 2009, at 7:19 AM, Ryan Chan wrote:
Hello, I have install latest Drupal, I come across with a problem: If I move the content of .htaccess into httpd.conf, the site is not accessible and error "HTTP 400 - BAD REQUEST" will be give out. If I leave the drupal config as in .htaccess, it is okay.
Did you remember to wrap the content from your .htaccess inside its own "Directory" directive?
<Directory /path/to/site> # .htaccess content goes here </Directory>
Just a stab in the dark guess. About the best I can do without looking at your files.
Steve
Hello,
On Sun, Jul 26, 2009 at 1:00 AM, Steven Scottensteves@splicer.com wrote:
On Jul 25, 2009, at 7:19 AM, Ryan Chan wrote: Did you remember to wrap the content from your .htaccess inside its own "Directory" directive?
<Directory /path/to/site> # .htaccess content goes here
</Directory>
Just a stab in the dark guess. About the best I can do without looking at your files.
Thanks.
This work, but before I wrap by a virtualhost, don't know why it didn't work though.
Thanks anyway.
Ryan Chan wrote:
Thanks.
This work, but before I wrap by a virtualhost, don't know why it didn't work though.
Thanks anyway.
You can put the rules in the VHost directive, but they still need to be wrapped in the directory directive. That allows you to specify different rule sets for different directories in that virtual host (the same as having .htaccess in the document root, then another .htaccess in /files). When putting the rules in the VHost directive you still need to specify the absolute path to each directory.
Jamie Holly http://www.intoxination.net http://www.hollyit.net