Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I am trying to follow appropriate procedure, so, here I am submitting a potential bug report. If I am doing this wrong, sucks to be me.
The problem is my IE users whom are using HTMLArea (great editor in Firefox, by the way) receive this error when trying to submit content, both editing exisiting and new (blank too) content: "Terminated request because of suspicious input data".
It looks like this has been reported in the past. Here is a thread I have located which seems to be the most appropriate: http://drupal.org/node/11759
I have boiled down two computers that have this problem with IE. Here is some common info:
Windows XP Home
IE 6.0.2900.2180.XPSP2
Drupal 4.5.0
the latest HTMLArea 4.5.0
I hope this helps. If you require more, just let me know.
Comments
Comment #1
shane birley commentedThird computer reports problem. This one is the latest IE (same as above) except on a Windows XP Professional machine.
Comment #2
shane birley commentedI just ran a wee test using Internet Explorer (same versions as above on WinXP Pro) and it terminated me. The log reads the following (and yes this is a fresh, blank document):
view details
Type warning
Date Thursday, December 2, 2004 - 1:31pm
User Test User
Location /node/add/blog
Message Terminated request because of suspicious input data:
Comment #3
shane birley commentedI could be barking too loudly, since I found this: http://drupal.org/node/8805
Just trying to help.
Comment #4
shane birley commentedBut, I don't know if the CVS currently has a "new" fix? Since the only posting I see is the one I just posted and it is from September and the problem is still occurring?
Comment #5
shane birley commentedIncidently, my post with the "head" tags was "terminated" by this site. I thought that was interesting and I am NOT using HTMLarea here. So, could this not be an HTMLarea problem and a Drupal core problem?
Comment #6
shane birley commentedNever mind. I think the code for the HTMLarea software puts in the HEAD and BODY tags all by itself and has nothing to do with Drupal.
I am sure everyone knew this, but I am just working through it. Seems odd to have to filter out HEAD tags as "allowed".
Comment #7
gordon commentedI think this is a php configuration issue. I have had this on drual.org when triing to post an example of an issue. I could post it at home, no problem.
What is the content that you are triing to post?
The other issue that you refer to comes into effect when the page is triing to load. This has since been fixed in both drupal and htmlarea, which now loads all the plugins from onload.
Would I be able to test this for myself? give me an url and I will try it. If you do not want to give me write access create a htmlarea demo page much like on my web site http://www.heydon.com.au?q=htmlareademo the source code is all there just cut and paste it.
Comment #8
Capnj commentedGordon said "I think this is a php configuration issue."
May be right. I have four sites. Three work, even with MSIE 6. One does not. The one that does not work is on a different server, although with the same host (lunarpages.com). The installations are identical in all other respects, but it's possible that the .htaccess files are not the same and that a PHP setting differs.
gil
Comment #9
gordon commentedI did some more investigation and drupal does do some checking, take a look in common.inc at valid_input_data(), This may be what is causing it, or at least the a good place to start looking.
Cause I can't replicate in on my test system it is hard to work out exxactly what is going wrong.
Comment #10
shane birley commented