<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Curing &#8216;Symbolic link not allowed&#8217; (Apache 2.0)</title>
	<atom:link href="http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/</link>
	<description></description>
	<lastBuildDate>Fri, 19 Feb 2010 13:50:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Drew</title>
		<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/comment-page-1/#comment-1067</link>
		<dc:creator>Drew</dc:creator>
		<pubDate>Thu, 27 Aug 2009 22:39:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.deckerd.com/curing-symbolic-link-not-allowed-apache-20/#comment-1067</guid>
		<description>Habib,

What does your error logs for Apache say?  Usually you can find out what the error logs are telling you and do a simple search on the error on Google, and figure it out pretty fast.  Let me know if you still need some help.</description>
		<content:encoded><![CDATA[<p>Habib,</p>
<p>What does your error logs for Apache say?  Usually you can find out what the error logs are telling you and do a simple search on the error on Google, and figure it out pretty fast.  Let me know if you still need some help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Habib</title>
		<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/comment-page-1/#comment-1056</link>
		<dc:creator>Habib</dc:creator>
		<pubDate>Fri, 17 Jul 2009 18:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.deckerd.com/curing-symbolic-link-not-allowed-apache-20/#comment-1056</guid>
		<description>Hi,
I&#039;m having the same problem. I have my DocumentRoot directory on the local filesystem. However, I cannot follow the links! My DocumentRoot is /web and here is the permission for it:

&lt;code&gt;drwxrwxrwx 3 root apache 4096 Jul 17 11:09 /web&lt;/code&gt;

In /web directory I have a symlink:
&lt;code&gt;lrwxrwxrwx 1 root root 31 Jul 16 17:00 /web/habib.html -&gt; /home/habib/web/habib.html&lt;/code&gt;

Permissions for /web (DocumentRoot) and other directories:
&lt;pre&gt;
&lt;code&gt;
drwxrwxrwx 3 root       root        0 Jul 17 10:33 /home
drwxrwxrwx 2 habib groupa 64 Jul 17 10:58 /home/habib
drwxrwxrwx 2 habib groupa 64 Jul 16 17:04 /home/habib/web
-rwxrwxrwx 1 nfsnobody  nfsnobody  69 Jul 16 16:57 /home/habib/web/habib.html
&lt;/code&gt;
&lt;/pre&gt;

As you can see, I have read, write and execute permissions on all files and directories.

And here is from my httpd.conf:
&lt;pre&gt;
&lt;code&gt;
User apache
Group apache

Options FollowSymLinks
AllowOverride None

Options Indexes FollowSymLinks
AllowOverride None

Order allow,deny
Allow from all
&lt;/code&gt;
&lt;/pre&gt;

Would you help me please?

Thanks.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
I&#8217;m having the same problem. I have my DocumentRoot directory on the local filesystem. However, I cannot follow the links! My DocumentRoot is /web and here is the permission for it:</p>
<p><code>drwxrwxrwx 3 root apache 4096 Jul 17 11:09 /web</code></p>
<p>In /web directory I have a symlink:<br />
<code>lrwxrwxrwx 1 root root 31 Jul 16 17:00 /web/habib.html -> /home/habib/web/habib.html</code></p>
<p>Permissions for /web (DocumentRoot) and other directories:</p>
<pre>
<code>
drwxrwxrwx 3 root       root        0 Jul 17 10:33 /home
drwxrwxrwx 2 habib groupa 64 Jul 17 10:58 /home/habib
drwxrwxrwx 2 habib groupa 64 Jul 16 17:04 /home/habib/web
-rwxrwxrwx 1 nfsnobody  nfsnobody  69 Jul 16 16:57 /home/habib/web/habib.html
</code>
</pre>
<p>As you can see, I have read, write and execute permissions on all files and directories.</p>
<p>And here is from my httpd.conf:</p>
<pre>
<code>
User apache
Group apache

Options FollowSymLinks
AllowOverride None

Options Indexes FollowSymLinks
AllowOverride None

Order allow,deny
Allow from all
</code>
</pre>
<p>Would you help me please?</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dean</title>
		<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/comment-page-1/#comment-980</link>
		<dc:creator>dean</dc:creator>
		<pubDate>Fri, 07 Nov 2008 16:45:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.deckerd.com/curing-symbolic-link-not-allowed-apache-20/#comment-980</guid>
		<description>Setting every directory to executable all the way down from the root to the directory I was linking to did the trick for me. THANK YOU VERY MUCH!!!</description>
		<content:encoded><![CDATA[<p>Setting every directory to executable all the way down from the root to the directory I was linking to did the trick for me. THANK YOU VERY MUCH!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/comment-page-1/#comment-956</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Wed, 29 Oct 2008 21:23:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.deckerd.com/curing-symbolic-link-not-allowed-apache-20/#comment-956</guid>
		<description>qw(Add a new (larger) disk to the system, format it accordingly, migrate the old /var/ mount-point to the new partition and change the DocumentRoot in the Apache configuration. This requires backing up old files and pushing them to the new partition and reconfiguring a small part of Apache; could cause a lot of downtime.)

If you have the luxury of being able to add a seprate partion to the system it&#039;s actually way easier than this and doesn&#039;t require reconfiguring apache.

add the new partition to the system (however you are going to do that based on your hardware)
mount it temporarily at something like /mnt/myNewDisk or just /mnt (see man mount)
*Take a backup*
move all the files from /var/www (or whatever your web dir is.
mv /var/www/* /mnt/myNewDisk/
unmount said new disk 
umount /mnt/myNewDisk
remount it on the now empty /var/www/ which makes a great mount point
edit your fstab (or vfstab) file to ensure this mounts at startup.

I&#039;m leaving out details on things like mount and fstab because they are a little os/vendor/filesystem specific. Generally they are pretty similar but you may need to brush up on the man page. In a pinch the /etc/fstab or /etc/vfstab can give you the options that you need but you&#039;ll have to double check your syntax for the command line.</description>
		<content:encoded><![CDATA[<p>qw(Add a new (larger) disk to the system, format it accordingly, migrate the old /var/ mount-point to the new partition and change the DocumentRoot in the Apache configuration. This requires backing up old files and pushing them to the new partition and reconfiguring a small part of Apache; could cause a lot of downtime.)</p>
<p>If you have the luxury of being able to add a seprate partion to the system it&#8217;s actually way easier than this and doesn&#8217;t require reconfiguring apache.</p>
<p>add the new partition to the system (however you are going to do that based on your hardware)<br />
mount it temporarily at something like /mnt/myNewDisk or just /mnt (see man mount)<br />
*Take a backup*<br />
move all the files from /var/www (or whatever your web dir is.<br />
mv /var/www/* /mnt/myNewDisk/<br />
unmount said new disk<br />
umount /mnt/myNewDisk<br />
remount it on the now empty /var/www/ which makes a great mount point<br />
edit your fstab (or vfstab) file to ensure this mounts at startup.</p>
<p>I&#8217;m leaving out details on things like mount and fstab because they are a little os/vendor/filesystem specific. Generally they are pretty similar but you may need to brush up on the man page. In a pinch the /etc/fstab or /etc/vfstab can give you the options that you need but you&#8217;ll have to double check your syntax for the command line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Drew</title>
		<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/comment-page-1/#comment-911</link>
		<dc:creator>Drew</dc:creator>
		<pubDate>Sun, 07 Sep 2008 03:33:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.deckerd.com/curing-symbolic-link-not-allowed-apache-20/#comment-911</guid>
		<description>Guys (and Gal),

Thanks for the feedback.  Of course you can disable SELinux, or just set the correct permissions for SELinux to work nicely with Apache.  Keep up the comments!

Regards,
Drew</description>
		<content:encoded><![CDATA[<p>Guys (and Gal),</p>
<p>Thanks for the feedback.  Of course you can disable SELinux, or just set the correct permissions for SELinux to work nicely with Apache.  Keep up the comments!</p>
<p>Regards,<br />
Drew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/comment-page-1/#comment-904</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 30 Jul 2008 19:53:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.deckerd.com/curing-symbolic-link-not-allowed-apache-20/#comment-904</guid>
		<description>Basically make it even more clear that you just need issue below 
#chmod -R 755 /data
#chmod -R 755 /data/www
#chmod -R 755 /data/www/newdirectory

for you SElinux, you can run 
#getsebool -aef&#124;Grep httpd 

to check the if it block it.
However, THANK YOU SO MUCH for this documentation.</description>
		<content:encoded><![CDATA[<p>Basically make it even more clear that you just need issue below<br />
#chmod -R 755 /data<br />
#chmod -R 755 /data/www<br />
#chmod -R 755 /data/www/newdirectory</p>
<p>for you SElinux, you can run<br />
#getsebool -aef|Grep httpd </p>
<p>to check the if it block it.<br />
However, THANK YOU SO MUCH for this documentation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janet</title>
		<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/comment-page-1/#comment-899</link>
		<dc:creator>Janet</dc:creator>
		<pubDate>Wed, 16 Jul 2008 16:00:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.deckerd.com/curing-symbolic-link-not-allowed-apache-20/#comment-899</guid>
		<description>THANK YOU Jose.  It works fine after i did echo 0 &gt; /selinux/enforce</description>
		<content:encoded><![CDATA[<p>THANK YOU Jose.  It works fine after i did echo 0 &gt; /selinux/enforce</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jose</title>
		<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/comment-page-1/#comment-895</link>
		<dc:creator>Jose</dc:creator>
		<pubDate>Tue, 01 Jul 2008 17:34:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.deckerd.com/curing-symbolic-link-not-allowed-apache-20/#comment-895</guid>
		<description>I had the same situation described here with a RHEL installation. I thought I had all permissions correct, but still the same Forbidden error. I followed the comments here and did a chown to apache, but still the problem! 
After some more searching we found about SELinux causing havoc like this. We turned this off issuing &quot;echo 0 &gt; /selinux/enforce&quot; and all is working. I haven&#039;t done more research to see how you can have this ON while still getting the above working, but for those out there who just need to get it going give this a try.</description>
		<content:encoded><![CDATA[<p>I had the same situation described here with a RHEL installation. I thought I had all permissions correct, but still the same Forbidden error. I followed the comments here and did a chown to apache, but still the problem!<br />
After some more searching we found about SELinux causing havoc like this. We turned this off issuing &#8220;echo 0 &gt; /selinux/enforce&#8221; and all is working. I haven&#8217;t done more research to see how you can have this ON while still getting the above working, but for those out there who just need to get it going give this a try.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janet</title>
		<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/comment-page-1/#comment-893</link>
		<dc:creator>Janet</dc:creator>
		<pubDate>Mon, 16 Jun 2008 19:46:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.deckerd.com/curing-symbolic-link-not-allowed-apache-20/#comment-893</guid>
		<description>sorry line 551 should be 
and line 556 should be </description>
		<content:encoded><![CDATA[<p>sorry line 551 should be<br />
and line 556 should be </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janet</title>
		<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/comment-page-1/#comment-892</link>
		<dc:creator>Janet</dc:creator>
		<pubDate>Mon, 16 Jun 2008 19:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.deckerd.com/curing-symbolic-link-not-allowed-apache-20/#comment-892</guid>
		<description>551	
   552	    AllowOverride None 
   553	    Options All 
   554	    Order allow,deny
   555	    Allow from all
   556	</description>
		<content:encoded><![CDATA[<p>551<br />
   552	    AllowOverride None<br />
   553	    Options All<br />
   554	    Order allow,deny<br />
   555	    Allow from all<br />
   556	</p>
]]></content:encoded>
	</item>
</channel>
</rss>
