Create an account

Very important

  • To access the important data of the forums, you must be active in each forum and especially in the leaks and database leaks section, send data and after sending the data and activity, data and important content will be opened and visible for you.
  • You will only see chat messages from people who are at or below your level.
  • More than 500,000 database leaks and millions of account leaks are waiting for you, so access and view with more activity.
  • Many important data are inactive and inaccessible for you, so open them with activity. (This will be done automatically)


Thread Rating:
  • 622 Vote(s) - 3.55 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Wordpress Options FollowSymLinks error

#1
I have a website setup in my /httpdocs directory with it's own htaccess and I have a wordpress blog within /httpdocs/blog, using the standard wordpress htaccess

I keep seeing the following error in my apache error log:

[error] [client #.#.#.#] Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that RewriteRule directive is forbidden: /var/www/vhosts/somedomain.com/httpdocs/blog/index.pl

I added "Options +FollowSymLinks" as this seems to have fixed the problem for others (but not me)

The main .htaccess is as follows:

The Wordpress .htaccess is:

Options +FollowSymLinks
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog/index.php [L]
</IfModule>
# END WordPres

I am also wondering why the error is reported as "index.pl" since there are no perl scripts in /blog. So, after some searching, I found an httpd.include file (plesk generated) in the /var/www/vhosts/somedomain/conf/ which contains some perl handler stuff:

<Files ~ (\.pl$)>
SetHandler perl-script
PerlHandler ModPerl::Registry
Options ExecCGI
allow from all
PerlSendHeader On
</Files>

If I remove perl support via Plesk, thus removing the above block of code, then I don't get errors anymore.

The obvious answer would be to disable perl as I don't need it, however there must be a way to fix this error without having to do that?
Reply

#2
add to .htaccess

Options FollowSymLinks

all done :)
Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

©0Day  2016 - 2023 | All Rights Reserved.  Made with    for the community. Connected through