Serious MySQL Problem

[EricGT]

Hi folks. This isn't a vBulletin problem, strictly speaking, but it is causing a lot of trouble with my development plans for my vBulletin site. I am really hoping someone here some insight into what is going on.

I recently changed to new servers and to MySQL 5.0.62, at the same time. Everything is working properly except for one very troublesome thing: I cannot edit and save any template containing a '< script >' tag, or add any content containing that tag to any template. When I try, the process times out and when I reopen that template, it is blank. This isn't just a vBulletin problem though. I get the same thing if I try to edit or modify and database field that already contains a script tag, or if I try to insert one.

I've experimented and trying to add '<script' causes the failure, while trying to add '<scrip' does not. It is the first part of that tag specifically causing this failure. This is bizarre. I've been using MySQL for eight years and I have never seen anything like this. Does anyone have any ideas on what could be causing this(I hope, I hope)? I am stumped. I appreciate any help any of you could provide. Eric

[Yours]

vBulletin requires MySQL4 or later to work properly. If you are using an older version then you are lucky vBulletin is working at all.

[EricGT]

Well, I solved this one myself. The Intrusion Protection System on my firewall was seeing the script tag in the packet sent to the MySQL server and killing it. DOH!:o No wonder no one is talking about the problem anywhere I could find. Well, it is easy enough to fix. Sometimes this stuff can be frustrating, but it always feels good to track down the problem. Thanks anyway, for the help. Eric

--------------- Added 1198705831 at 1198705831 ---------------

vBulletin requires MySQL4 or later to work properly. If you are using an older version then you are lucky vBulletin is working at all.

That should have said '5.0.62'. That was a typo, on my part. Anyway, it turns out that my firewall's intrusion detection system was the culprit. Thanks for the reply though. Eric

[TECK]

I wonder who do you know at MySQL to get this version (5.0.62)... when the latest is 5.0.51
It is good to know Uncle Lenny... forgetaboutit :D

[EricGT]

I wonder who do you know at MySQL to get this version (5.0.62)... when the latest is 5.0.51
It is good to know Uncle Lenny... forgetaboutit :D

Oops. That is another typo. It should read '5.0.32'. That is the default install version for the stable distro of Debian Linux. Sorry about that. Eric