Geeklog Forums

Help me out here. I've discovered a repeatable error, works every time, happened with 1.3.11sr and just happened again after having upgraded to 1.4.0 - here it is;

If I used the word "from" anywhere in the text of an article, I get this:

"Forbidden
You don't have permission to access /admin/story.php on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


--------------------------------------------------------------------------------

Apache/1.3.33 Server at www.panama-guide.com Port 80"

I can take out the word "from" and the article saves just fine. I can put it back in, and get the error. Works every time. Funny, as I type this, I'm wondering if I'll get the error here... Let's see...

Just wondering if anyone has taken a look at this "from" thing. It's real. I'm running 1.4 on the professional theme, and every time I use the word "from" in the text of an article, I get an error message and can't post the article. If I just go back and remove "from" from the article it works fine, every time.

Any ideas? Is there anything I can do to get this word back into my vocabulary?

I'm having the same exact error message. Unfortunately, I can't get it to stop happening by removing the word 'from'. I haven't isolated it yet - it seems like it has to do with the *length* of the story for me. This is a particularly long story (for me), and I can save fine until I go over about 3620 characters - doesn't matter what those characters are I don't think. I'm still on 1.4.0sr3. Any changes in newer releases to story.php that might make this happen? I'm going to upgrade next just to see what happens.

OOps. Seems it's a similar issue after all - in my case, the word is 'iframe' (I was writing about web tech) and if I leave that word out all is good. Any ideas, Dirk?

In any case, the problem seems to have gone away with the most recent upgrade of the GL software and security releases. Must have been some kind of a bug...

I can't imagine anything in Geeklog triggering such a behavior and error message. IMHO, it must have been something on the server, e.g. some sort of monitoring software to prevent attacks. If this were on Apache 2, I would have said it could be mod_security. But since the original incident was on Apache 1.3, I have no idea.

bye, Dirk

My issue was on
Apache 1.3.37 (Unix)
PHP Version 5.1.4
Linux 2.4.21-47.ELsmp
It's really not a big deal, I just changed the word to i-frame and it worked fine, but would be nice to know what's happening.