MikeJ

I'll be scared if Head Guru's picture doesn't change...

Naughty Naughty Naughty Naughty Naughty Naughty

What?!? You didn't make enough to share?!?!

TCH needs a chatroom, so we can all sit online and chat in anticipation before 10pm.

That one's a given. They announced a while ago that the reseller prices go up starting today.

A back alley. Some guy in a trenchcoat was selling domains cheap. No... all my domains are with godaddy.

Ok... then my countdown is working. woooot

Yea, I said the 5:33 (now 5:11), and my computer is set to CST. Maybe the actual time something happens is a mystery too...

Hmm... my clock's set right. My system periodically polls a reliable time source. As of this post, I'm showing 5 hours, 33 minutes.

Hmmm...what's showing up for me is 6:36 to go. Which means about 9pm my time (CST), 7pm West Coast (I'm assuming your talking about the U.S.?)

Hmm.... thinking about it.... I've owned, in order, a Ford, Pontiac, Chevy, Pontiac, Ford, Chevy, Toyota, Chevy, Chevy. I don't quite qualify for all American. <_< And my motorcycle is a Suzuki, so I kinda lose points there too.

Speaking as a customer of theirs but who had a reseller account before upgrading to dedicated server (and helped other resellers): 1. Yes, not a problem. 2. No. Your bandwidth allocations can't exceed your total, otherwise it will prevent you from creating another account. Same goes with diskspace. (I'm 99% certain of this...someone will correct me if I'm wrong). 3. You can resell all you want on a dedicated server. I moved my own accounts, but TCH is very flexible and I believe they would help you move the accounts over. 4. If you have your own DNS servers, you can use them instead of TCH. If it's the nameserver names you want to use, but pointed at TCH nameservers, you have to have the standard reseller plan or above.

At that level of complexity, it might be easier just to write a script to manage .htaccess hotlink stuff... a more advanced version of the cPanel one. Maybe I'll do that sometime when I have a bunch of free time on my hands.

It looks like you'll have to apply the RewriteCond's to every line... or compress lines. You could write your one line as this (yes, I'm going to break the board's formating most likely): >RewriteRule ^/*images/+(text\.jpg|title\.jpg|title_alternate\.jpg|advertisements/+(omgnbox\.jpg|omgnbrick\.jpg|omgnbanner\.jpg|omgntower\.jpg)|web/+(88x30\.jpg|88x31\.jpg|100x60\.jpg|468x60\.jpg|125x600\.jpg))$ http://www.omgn.com/images/undef.gif [R,NC] Assuming ()'s can be nested (I haven't tried it). Otherwise, you can do the same without the nested ()'s but it gets a bit longer.

Ahh...I think I know what's wrong... let me chew on it for a moment. I think the RewriteCond's are only applying to the first RewriteRule. Need to relook at that and see how to make it apply for all... Edit: Yea...what you said.

Something's not quite right yet, though: http://www.omgn.com/ I'm seeing "Image Hotlinking Disabled" for a couple of your images. Do you have your RewriteCond's correct?

I should also point out that if you have domains parked, you will need to add those as well as allowed HTTP_REFERER's. The ! means NOT. So the conditions are that the referer is NOT one of those listed for the redirection or blocking to take effect.

I believe this will work for you: >RewriteEngine on RewriteCond %{HTTP_REFERER} !^http://******/.*$ [NC] RewriteCond %{HTTP_REFERER} !^http://******$ [NC] RewriteCond %{HTTP_REFERER} !^http://www.******/.*$ [NC] RewriteCond %{HTTP_REFERER} !^http://www.******$ [NC] RewriteRule ^/*file1\.gif$ http://******/images/nohotlink.jpg [R,NC] RewriteRule ^/*images/+file2\.jpg$ http://******/images/nohotlink.jpg [R,NC] RewriteRule ^/*images/+other/+file3\.png$ http://******/images/nohotlink.jpg [R,NC] The above example will block hotlinking to the following files assuming this is in the .htaccess file located in /public_html (* used to prevent this forum from autolinking): h*tp://******/file1.gif h*tp://******/images/file2.jpg h*tp://******/images/other/file3.png Instead, h*tp://******/images/nohotlink.jpg would be displayed. If you want to just prevent access with no redirection, change the RewriteRule lines to resemble this: >RewriteRule ^/*file1\.gif$ - [F,NC] Legend: ^ = start of line anchor (basically reference to where .htaccess is located) $ = end of line anchor (nothing exists past this) * = 0 or more of the proceeding text + = 1 or more of the proceeding text \ = escape for special characters (. without \ means match any char, not just dot). [R] = Redirect [F] = Forbidden [NC] = No Case (ignore case in matching... remove NC if you want specific case to be matched) I used /* and /+ in the examples above to prevent someone from simply bypassing the hotlink protection by linking something like "h*tp://******/images//file2.jpg" since the webserver will still deliver the image, but it wouldn't match the rewrite rule if it was only looking for a single /. Again, try it, see if it works for you. If you have problems, I can probably help you troubleshoot it.

woooot Congrats, Andrew!!!!!!!!! May Nathan James grow up to be a healthy and joyful human! Diapers... Yuck!

This looks like it will work for you: >RewriteEngine on RewriteCond %{HTTP_REFERER} !^http://******/.*$ [NC] RewriteCond %{HTTP_REFERER} !^http://******$ [NC] RewriteCond %{HTTP_REFERER} !^http://www.******/.*$ [NC] RewriteCond %{HTTP_REFERER} !^http://www.******$ [NC] RewriteRule (^|.*/)(file1\.gif|file2\.gif|file3\.jpg|file4\.png)$ http://******/images/nohotlink.gif [R,NC] This will disallow hotlinking for any instance of file1.gif, file2.gif, file3.jpg, and file4.png. Change as appropriate, noting that "|" is an OR, and dots need to be escaped with a "\". So for a file named "myimage.gif", it needs to be type in the rule as "myimage\.gif". Obviously change the "******" instances, and you can change the redirect URL to whatever you need. If you need to do it for a specific files with the whole path included (as opposed to any instance of the file), let me know and I can test something out and give you an example for that tomorrow probably. Btw, I don't consider myself a rewriting "expert" so test this fully after you install it. It passed all the tests I did, but I could still have messed something up.

You'll get a welcome email that will explain how to access the account before you change your DNS. And if you get too stuck, just make another post asking for help. I've moved over a dozen domains by setting up the new accounts, copying all the contents over, testing them, and then cutting DNS over.

Then you're going to have to modify the RewriteRule >RewriteRule .*\.(jpg|jpeg|gif|png|bmp)$ - [F,NC] Take a look at the rewriting guide. If there's anything common in the file names that will help a lot, otherwise you are going to have to include each file name.

Create a hotlink protected directory (or directory tree) and enable hotlink protection there (you'll have to edit the .htaccess manually). See this thread. If you want to redirect to another image, just make sure it's not in a hotlink protected directory.

Are you going through any proxy server by any chance? Maybe you have some external device caching it???

Yes, assuming the directory also allows access, but they would have to know your account name (TCH uses somewhat cryptic account names on creation) and that you are on the same server (home directory by default is not "listable" by regular accounts).