quick .htaccess issue
 

i'm installing a program on a virtual server (may be shared though) and keep running into issues with the htaccess dictacting mod rewrites long after the file is deleted or replaced with a new one or deleted and then replaced with a new one (not a browser cache issue)

anybody ever run into this?

views: 3

should have posted a pic with it

It's either a browser cache issue, as you mentioned... Or the .htaccess is invisible, leaving you to only think you have deleted it.

If you use WS FTP, type:

-la

into the white field on the right hand side of the transfer windows. That will enable you to see files without names (.htaccess, .htpasswd, etc).

playing around a little more, it's actually replacing the the .htaccess after i upload it with the old one. permissions issue?

supposed to be root

Try to replace the offending .htaccess with an empty one instead of deleting it then. If that fails, check the .htaccess for hotlink protection, your server software may be set on hotlink-protecting your domain. If it does contain this, just edit out the parts you don't want and leave the protection.

Or, of course, go to WHM or whatever management software you use and disable the automatic .htaccess options. It's better to do it manually any way.

deleting the htaccess content didn't work, ended up having to create a new empty file and replace it with that, and then dl that, change the content and reupload

thanks for putting me on the right path. not my server so i don't even know if whm is on there, do virtuals generally have problems like this?

Ok, as long as you got it worked out. Virtuals have many problems, and I am glad I moved away from that a long time ago. I made a script once that let me download every last file on a server, including the script source codes and mySQL dbs of other sites and even system files. It worked on quite a lot of servers, I even tried a few adult ones. The sad thing is that this wouldn't be possible if whoever governed the servers would read through the php config and set some restrictions.

i was in wsftp and just had to change the directory from sitea.com/htdocs to siteb.com/htdocs, server had almost 500 sites on it

a bit unsettling

i like hiding behind the false sense of security from a managed server