Free Ringtones - Free eBooks Download - Car Insurance - Fast Loans - Flights

PDA

View Full Version : .htaccess at godaddy


WhatiFind
Mar 4th 2005, 4:07 am
I have a small problem, I'm using the biz-directory script, I found a rewrite module for .htaccess so the urls are rewritten to /1.php, /2.php and so on.
Got things working until I moved the site to a godaddy account. Here is the .htaccess code: RewriteEngine on
RewriteRule ^([0-9]+).php$ index.php?c=$1& [L]
RewriteRule ^([0-9]+)add.php$ add_url.php?c=$1& [L]
So I contacted godaddy support about this problem and they told me this:
If you feel comfortable doing so, you can create an .HTACCESS file to password protect a directory in your Linux hosting account. We cannot provide instructions or troubleshooting for this, but we can tell you that tutorials and password generators can be found through a web search, and your full server path is /home/content/u/s/e/username/html, where 'u', ’s’, and 'e' are replaced by the first three letters of your hosting username, and 'username' is replaced by your username. I don't quite get this, now I know the servers path but how do I put this into .htaccess and get it to work?
Did various searches around the internet for tutorials or examples but I didn't found anything that solves my problem.

Does any one has experience with using .htaccess/mod_rewrite at godaddy accounts or knows how to solve this problem?

nevetS
Mar 4th 2005, 4:15 am
If it worked previously, but not at godaddy, you are more than likely out of luck.

In order for rewrite rules to work in a virtual host directory, it needs to be configured with the "Options FileInfo" directive in apache.

If that is the response they gave you, they are not likely to change things for you.

yfs1
Mar 4th 2005, 4:23 am
Nevet is right..GoDaddy will not make the necesary changes (I've gone down that road before)

digital01101
Apr 25th 2005, 11:54 pm
I have a big problem with godaddy hosting
I put .htaccess file and it blocked access for every type of file(jpg,txt,html..etc) but it didnt block access for .php files and I dont understand why

The same htaccess I put it on different ather hosts(I tried 5 hosts...my friends hosts) and there it blocked everything(php files too)

Support from godady said that they cant help me with this problem

AuthUserFile ................../htaccess

AuthName "mypage"
AuthType Basic
<Limit GET POST>
order allow,deny
allow from all
deny from xxx.xxx.xxx.xxx
</Limit>


I also tried this

AuthUserFile ........................../htaccess

AuthName "mypage"
AuthType Basic
<Limit GET POST>
<Files ~ "^.*\.([Pp][Hh][Pp])">
order allow,deny
allow from all
deny from xxx.xxx.xxx.xxx
</Files>
</Limit>

It blocks access for every type of file but not for .php files

I also tried

<Files ~ "^.*\.(PHP|php)">

The same problem...can you try this on your godaddy account and tell me if U have the same problem with php files?

Godaddy support says the same thing :we cant help u with this :eek:
If they can help me with this simple thing why give money to them when on
ather hosts this is working fine and a lot of ather weird problems that I have on godaddy I dont have on ather hosts

yfs1
Apr 26th 2005, 1:29 am
Its public knowledge that GoDaddy won't support what you are looking to do. Furthermore, they will tell you that flat out from the begginning whether you are a customer or not.

This is the comprimise to have dirt cheap hosting. This doesn't mean they suck. It just means they are after a certain market.

I personally host some of my simple sites with them and couldn't be happier. My other sites I pay more for hosting and get the attention they need.

Thats what I would suggest in this situation rather than blaming them.

WhatiFind
Apr 26th 2005, 3:33 am
The one thing that I kept seeing was you have to put up something like this in order to make it work: (in your .htacces) AuthUserFile /home/content/a/c/c/accoutname/html replace a/c/c/ with the first 3 letters of your account and replace accountname with your accountname.

I have learned that you cannot 'force' the servers of godaddy to do something with .htaccess and Godaddy will not change anything.

Well that's the price you have to pay with cheap hosting. I have one site hosted there and it's working fine.

shanX
Sep 15th 2007, 9:59 am
Thread bump :p

Seems like Gocrappy servers aren't passing on htaccess variables(([0-9]+), (.+)) :(

And they havent fixed it from 2005 :O

Has anyone got alternative solutions other than switching host??

ForumJoiner
Nov 3rd 2007, 1:24 pm
A question for all who encountered issues with .htaccess and GoDaddy: do you have multiple domains on the same hosting plan?

For instance, I couldn't make phpLD working with SEO names on domains that are hosted toghether, on the same account, but on separate folders, but I managed to make phpLD work just fine with domains that were pointed to the root of the hosting account.

I suspect that, in the first case, I didn't set-up properly RewriteBase in .htaccess, that's why it didn't work. I still don't know where to point that RewriteBase, and the logs I can see do not help me (I need the rewrite.log, which GoDaddy can't offer me).

login
Feb 3rd 2008, 4:04 pm
The problem with godaddy is that they dont support many things that are not 100% standard. Choose another host.

Yankee85
May 8th 2008, 10:15 pm
I wanted to buy GoDady hosting, but it seems that there are too many problems... :(

ForumJoiner
May 9th 2008, 2:39 am
Some things improved at GoDaddy. For instance, now I can run WordPress and Drupal without any problems (which didn't happen on the past).

It's important to know that if you create a .htacces in a folder, this file will be interpreted (taken into consideration by your program) within the next hour (not instantly). After understanding this, many problems were solved easily.

shanX
May 9th 2008, 9:34 am
I got a shared hosting account with Godaddy sometime back, I tried a script on it and had few issues along with the issue I have posted above. So I moved onto another. Later on, I uploaded the same script to a Godaddy dedicated hosting account for a client, it worked as expected. In that case I had to use RewriteBase on htaccess files, everything else worked fine. Seems like they have different configurations for different. But these kind of stuff are expected as standard ;)