Sorry, please ignore, I have to prove the most simple things to my new host [Thanks Stealth, they're not exactly smoking anymore]

Image #1 - upper case extension



Image #2 - lower case extension

fail with and without adblock

I've been thru this problem a couple times so far as you probably know. Just trying to get A2 Hosting to understand nothing has changed except that I'm now on their servers. And their answers as to why it's not working are mildly humorous and make no sense. It's not like I haven't been hotlinking pictures from my site for 18 years now on numerous sites [same problems on 6speed.com, probably sso I just haven't wandered over to try and find out, they probably won't work there either......] And I could use it fixed or I'll need to move to someplace that doesn't have an issue.

Don't you hate it the subject line doesn't have spell check? And that you're old enough the keyboard is too close and the monitor too far to see these danged letters clearly ;/

Eh, just ignire me.

Assuming hotlink protection is off or setup properly your site has an IP Addy shared with hundreds of others and thus might be caught in anti-spam filters. Also possible is them using a bandwidth saving cache system built into a2 servers. The giveaway is your local hosted images always work and cost is relatively cheap.

To summarize they seem ok for typical hosting of content and pages not intended to be hotlink and viewed from other sites.

Stealth. You out there?
You have any problem hotlinking from A2? Or were those JSART pics hosted somewhere else?
Like Stealth would look in an ignire thread.

Glen, you know I never understand when you speak geek.

Bottom line is, ball is in their court. Either they figure out why my chit don't work or I'll have to go someplace it does [and you know how much I like change.]

What is their response, this is ongoing for months. They might be a great host for most sites (who often don't want hotlinks) but maybe they don't meet your needs. The fast, cheap SSD angle raises obvious red flags.

Also does stealth have a dedicated server and or I.P. addy

Those SSD's are the reason I immediately didn't look any further.

They keep going on about how the upper case extension is not working with the forum software, and it's trying to read it as a page.

Check this out, one of my pics will actually hotlink now

And then I hit refresh and the picture disappeared, it was in my cache and showed it. I got all excited for nothing ;/

It was there then refresh and gone. Upper lower is moot these are being blocked on load or reload on pages outside ibanezrules.com.

That photo bucket works without fail summarizes the problem.

Glen, could you do a translation for me into English?

After further investigation into your .htaccess rewrite rules, this is being caused by the RewriteRule Flag "- [F]" that you have in your .htaccess files for images. This RewriteRule Flag forces the current URL to be forbidden, i.e., it immediately sends back a HTTP response of 403 Forbidden.

As an example in the below .htaccess file, I commented out line 7 and added line 8 using the RewriteRule Flag L.

/home/ibanezru/public_html/images/jemsite/.htaccess

The images from that directory are now loading on the below URLs.

http://www.jemsite.com/forums/f10/pl...re-148226.html
http://www.jemsite.com/forums/f36/ho...ld-147730.html

You or your developer will need to further review all of your .htaccess rewrite rules to ensure they are written to suit your specific needs.


That's how they fixed the first folder, of course this seems to only fix 1 folder as the picture of the JS2480 is nowhere to be seen.

So how id it these ata files are not working on this server, and considering how many there are - I probably have 40 different image folders, that contain hundreds of folders. if this access thing effects all folders it has to be changed in every folder?

Which begs the question isn't is easier to move to a server my files work on?

Easy fix, i can't believe they didn't check that months ago. That is overriding the cPanel hotlink setup*on an individual folder level.* Easier to edit the files than switch hosts.

Think of the .htaccess file is an optional security guard on each folder.

Except for root folder you don't need .htaccess in any public folder unless you want to prevent access (which can be done also via cpanel or the .htaccess file in root).

You can delete them all (except the one in the root folder and in folders where you don't want files to be hotlinked) and then optionally set/verify CHMOD 755 to each subfolder ... or edit each file as instructed. the L flag just stops the code ignoring what's below.

Are the .htaccess files being automatically created in new folders or more likely did you upload them not knowing what they do?