prjg

You don’t need even a password to view the RSS of your comments. Google has captured them too.

Why has it happened? RSS, probably. You might want to ask Google to remove thie entries for you if you are that concerned about them.

Add a “noarchive” flag to your robots meta if you dpn’t want anything cached.

Put the above rule in your doc_root too, not your /blog install, that way it captures everything. Works like a charm.
Rather than redirect to another site, my 403 page has a few choice words on it re: freeloading ??

My code, jsut for comparison’s sake:

RewriteEngine on
RewriteCond %{HTTP_REFERER} !^https://(www\.)?ulujain\.org [NC]
RewriteCond %{HTTP_REFERER} !google\. [NC]
RewriteCond %(HTTP_REFERER) !yahoo\. [NC]
RewriteCond %(HTTP_REFERER) !altavista\. [NC]
RewriteCond %{HTTP_REFERER} !alltheweb\. [NC]
RewriteCond %{HTTP_REFERER} !search\?q=cache [NC]
RewriteCond %{HTTP_REFERER} ^https:// [NC]
RewriteCond %{HTTP_REFERER} !^$
RewriteRule \.(jpe?g|gif|png)$ – [F]

Yep, it looks awful in IE. Just curious, is there any reason that little picture of John Kerry weighs in at 1.3Mb?

Wow, that did it! I had to mess with it a little to get around IE 6.0’s horror way of calculating margins and stuff, but it worked. I use FF as my browser, but still…

Thanks for your help.

You mean for the base URL of your blog? Yep, it was meant to be a full canonical URL, https:// and everything.

You have a mistyped relative URL somewhere or you’ve missed the https:// part in something. That’s what normally causes it.

I.e, if you make an anchor to say https://www.doesntexist.tld rather than https://www.doesntexist.tld it’ll appear as
https://www.robirwin.com/www.doesntexist.tld

The URL’s been borked somehow. If you look at your links, they re-duplicate, ie.
https://www.robirwin.com/iliketowatch/www.robirwin.com/iliketowatch

Disable the visual editor thingy, does that fix it? I’ve entered entities of all descriptions and WP has handled them with aplomb.

What’s the URL of your blog?

Yep, it loads fine for me too, IE 6.0, FF 1.5.0.1 and Opera 8.53

The obvious solution is to change hosts to one who does allow URL re-writing, but you’ve ruled that out. So, now you’re in search of a non-obvious solution and I wish you well. ??

Validation should be your first goal… it’s hard to diagnose problems without validation because of the different ways different browsers deal with invalid HTML.

You ought to see the way different browsers deal with valid HTML as well. ??

Are directory permissions set correctly? Sounds like something wasn’t chmod’ed correctly.

You’re right, it’s not elegant. The word “kludge” comes to mind, but whatever works for you.

BTW, pages looks OK to me, FF 1.5.0.1 on W2K. Just takes a little while to load (DSL from the other side of the world to the US)

It won’t die; they’ll be prompted what to do with the page and if they select open it with IE, any other instances “should” open automagically. Who knows, though?

Sorry, didn’t see this topic had been added to.

What I mean is that the minute the .htaccess rule is written and saved server-side, it becomes active. You’ll know if it’s valid or not, it’ll generate an internal server error otherwise.

You can’t access the file because .files are “hidden” files in Unix parlance and there’s a setting in apache that enforces this. That’s by design – it’s not meant to be toyed with remotely like WP allows you to.