Welcome to Geeklog, Anonymous Sunday, September 01 2024 @ 01:32 am EDT
Geeklog Forums
Use of the word "from" in article text causes error...
Status: offline
winnerdk
Forum User
Full Member
Registered: 04/24/05
Posts: 339
Location:Panama City, Republic of Panama
![Shocked Shocked](http://www.geeklog.net/images/smiles/icon_eek.gif)
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...
11
7
Quote
Status: offline
winnerdk
Forum User
Full Member
Registered: 04/24/05
Posts: 339
Location:Panama City, Republic of Panama
![Question Question](http://www.geeklog.net/images/smiles/icon_question.gif)
Any ideas? Is there anything I can do to get this word back into my vocabulary?
7
11
Quote
Status: offline
n4th4n
Forum User
Chatty
Registered: 07/21/03
Posts: 49
Location:NY, USA
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.
11
7
Quote
Status: offline
Dirk
Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Location:Stuttgart, Germany
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
bye, Dirk
10
8
Quote
All times are EDT. The time is now 01:32 am.
- Normal Topic
- Sticky Topic
- Locked Topic
- New Post
- Sticky Topic W/ New Post
- Locked Topic W/ New Post
- View Anonymous Posts
- Able to post
- Filtered HTML Allowed
- Censored Content