Quote Originally Posted by TheHYPO View Post
Verdict came back from tech support... "This was due to a problem with the way Apache works on this server. I've corrected it..."

Yeah, when they admit it's their fault, all of a sudden they are far less specific... I'm going to see if I can get any more information, but whatever "it" was, it's fixed.
Same thing here, today. Unfortunately, DrByte's excellent suggestion no longer works so I need to wait for webhost's support to answer the ticket I opened.

But in the webhost support forum, they already admitted that they have been experimenting with some mod_security rules... this is a production server, business account... Unbelievable.