Simply put I am having issues linking this sig to my signature here on the forums. It keeps giving me a 403 error.

Anyone know enough about .htaccess files to tell me what I am doing wrong?

This is the .htaccess for the root folder for the website

ErrorDocument 404 /notfound.html
ErrorDocument 403 /forbidden.html
Options -Indexes

This is the .htaccess file for the sigs directory

Options +Indexes
IndexIgnore *.htaccess
RewriteEngine on
RewriteRule ^.*$ -

I can load a directory listing just fine but can't view the image.

Any help would be great.

I get a 404 File Not Found when I try to view the sig just by clicking on it. Not sure what's up honestly.

I've been debating switching web hosts if I can't get the problem resolved because that is not the only problem I am having with them.

I'd log in via FTP and just double check that the file is still there. Also make sure the file name is exact (i.e. capitalization, etc.)

I'm on my phone right now but once I get to my pc I will check.

check the file name for unusual characters and ensure that the file extension matches the file type.

Also verify permissions.

Even the directory listing is showing no file for me.

I know a little about .htaccess. I have used it a little to secure my wordpress blogs. I don't fully understand everything though.

I do know that Options -Indexes disables directory browsing. That could be it. I have read that you can add it for security reasons. My hosting companies server configuration won't even allow me to put that in. I did some testing and if I put in Options -Indexes it does not take and gets commented out in my file and tells me that I cannot overwrite that function. To comment something out in .htaccess files just put a # in front of it with no spaces before or after. I learned this from tip #10 from this website:

http://www.smashingm...ecurity-tweaks/

IndexIgnore *.htaccess is not it because that is just saying hide the .htaccess file when listing the directory.

That brings it down to possibly being this code:

RewriteEngine on
RewriteRule ^.*$ -

I don't think you need that at all. It looks incomplete from all the ones I have reviewed. I say backup the .htaccess files and do some tests. I would removed the rewrite command above save it and see what happens. If that does not do it put it back in and then remove Options -Indexes from the other one, save and see what happens. Add it back in if no changes occured. At least you could pinpoint it down to the one that could be causing it. Just some suggestions. I have some experience with this but I am no expert with .htaccess. There are so many commands you could put in there it is insane. You should see one of my files it has alot in it. I just added and deleted things to experiment with mine and I never permanently broke my site. I did alot of google searches messing with this stuff.

I checked, the file is there...

I believe I got it working. Can someone confirm that they can access the directory and the image?

I'm not sure if the index is working or not, as it just takes me to a list with only "Parent Directory" in it and no items, but the other link to the image says "403 Forbidden

You do not have access to that part of the server."

It's hard to troubleshoot without really seeing everything, but here is an excellent guide on htaccess. It should let you know if it's a problem with it or not.

http://corz.org/serv/tricks/htaccess2.php

I will be sure to try that.

Looks like a permission thing. Getting 403 forbidden. Can you set permissions on the file?

I can view the directory listing but it displays nothing.

I am noticing for me that if I link to it, the image does not show, but if I go to it directly without the link then it works... sometimes that is...

I am noticing for me that if I link to it, the image does not show, but if I go to it directly without the link then it works... sometimes that is...

Could be intelligent browser caching that notices its the same file request from the same IP/Domain as when you log into admin backend.

I've had something similar happen to me when I was webhosting a college project. It did turn out to be permissions for me in the end so I still think its that even if it might be driving ya mad

Can you apply 777 permissions to it and post so we can check it and then scale back the permissions until you get to the relevant level? (I usually deal with windows permissions so don't know what the actual level should be off the top of my head).

Could be intelligent browser caching that notices its the same file request from the same IP/Domain as when you log into admin backend.

I've had something similar happen to me when I was webhosting a college project. It did turn out to be permissions for me in the end so I still think its that even if it might be driving ya mad

Can you apply 777 permissions to it and post so we can check it and then scale back the permissions until you get to the relevant level? (I usually deal with windows permissions so don't know what the actual level should be off the top of my head).

I have to head into work, but I will be sure to try that.

[edit] I put 777 on the image and the directory. Still doesn't appear to work.