Ok, which means this problem lately came about and I'm not sure why it is occurring it's really two problems in a single...

. My .htaccess file, for reference. (EDITED)

Options -Indexes +FollowSymLinks
RewriteEngine On
RewriteBase /

ErrorDocument 400 /index.php?400
ErrorDocument 401 /index.php?401
ErrorDocument 403 /index.php?403
ErrorDocument 404 /index.php?404
ErrorDocument 410 /index.php?410
ErrorDocument 414 /index.php?414
ErrorDocument 500 /global/500.php

RewriteCond %{HTTP_HOST} !^$ [NC]
RewriteRule .* index.php [L]

RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^https?://(.*\.)?(animuson)\.(biz|com|info|me|net|org|us|ws)/.*$ [NC]
RewriteRule ^.*$ - [F]

1. My 'pictures' folder is following a hard path rather than the redirect.

I've no clue WHY it's carrying this out. It is annoying me. The 'pictures' folder is really a symbolic connect to another place to ensure that I'm able to easily upload files to that particular folder without needing to sort through folders and the like via my FTP account, but that is the only real factor I apply it. However, after i visit http://example.com/pictures my htaccess sees it as being being able to access that other folder, that is restricted, and throws a 403 error instead of redirecting to index.php and exhibiting the page like normal.

I believed it's something related to that folder as being a symbolic link leading to it to do something oddly, however i have determined that my rules aren't being put on folders whatsoever. Basically visit folders for example 'css' and 'com' that are folders within the web root, it shows a 404 error page and adds the '/' towards the finish from the URL since it is dealing with it as being a directory. Additionally, it does exactly the same 403 error for my 'images' directory which is to establish within the same fashion.

So, the question this is how will i modify my RewriteRule to use towards the sites too? I would like everything utilized through the web to become rerouted to index.php while keeping the entire access path within the address bar, why do no longer working? (I am confident it had been working fine before.)

Here is a small chart to exhibit the pathways they are following...

example.com/pictures  -> pictures/ -> /home/animuson/animuson-pictures -> 403
example.com/com       -> com/      -> 404
example.com/test      -> index.php
example.com/          -> index.php
example.com/images    -> images/   -> /home/animuson/animuson-images   -> 403
example.com/css       -> css/      -> 404

EDIT: Following information added.
Apache is processing the dwelling from the directory first. It's identifying when the path is available according to that which was typed in to the address bar. If a person types inside a folder title that unexpectedly happens to exist, it'll redirect the consumer towards the path using the "/" in the finish from the URL symbols of it's a directory. For that 'pictures' directory described above, the consumer doesn't have permission to gain access to that folder so it's redirecting these to a 403 Access Refused page instead of simply showing the page that's supposed to become displayed there through the RewriteRule above. My greatest real question is exactly why is Apache processing your directory first and how do you allow it to be stop doing that? I'd love an response to this.

2. Exactly why is my compression no longer working? (EDIT: This part is bound.)

When examining my website via a web optimizer, it keeps saying my page is not using web compression, but I am almost 100% positive it was working fine before underneath the same configurations. Can anybody suggest any explanations why may possibly not work with this particular setup or suggest an easy method to do it?