Lounge of Tomorrow

Lounge of Tomorrow (http://74.208.121.111/LoT/index.php)
-   Beatnik (http://74.208.121.111/LoT/forumdisplay.php?f=9)
-   -   The Beatles - Love (http://74.208.121.111/LoT/showthread.php?t=4785)

Alex 10-12-2007 11:55 AM

Oh, and if you want to test it without having a lot of test posts show up. Type your test in the Quick Reply box and then rather than clicking "Post Quick Reply" click "Go Advanced". That also triggers the Forbidden message. If you get the advanced page then the text you entered will post.

DreadPirateRoberts 10-12-2007 12:49 PM

python_ is a programming language, I think something is catching the keyword and kicking it out.

Alex 10-12-2007 12:57 PM

But then it should do so generically on vBulletin.

DreadPirateRoberts 10-12-2007 12:59 PM

Quote:

Originally Posted by Alex (Post 165903)
But then it should do so generically on vBulletin.

I think it goes though Apache first, so I'm guessing it's in Apache.

Alex 10-12-2007 01:01 PM

Yep, that's what I just realized.

Alex 10-12-2007 01:03 PM

Note that putting python_ in any submitted form on LoT gets this result (search page, for example).

DreadPirateRoberts 10-12-2007 01:08 PM

This reminds me of BTD's signature


Alex 10-12-2007 01:11 PM

Can't quickly find anything on this specific method of producing the error but searching "apache forbidden python" will get you plenty of examples of it. Looks like it something in the Apache httpd.conf.

Don't know if that means going through the LoT hosting company or if that is something under direct control. (Assuming of course if something so random is worth the fix).

Personally, Lisa and I would probably be fine with anything that makes discussing Monty Not-Funny more difficult.

DreadPirateRoberts 10-12-2007 01:17 PM

We aren't the only ones. Here's what I found on the vbulletin site:

Error sending PMs with the word Python_ in them?

http://www.vbulletin.com/go/modsecurity

Alex 10-12-2007 01:27 PM

Damn. Your Google-fu is more powerful than mine today.

I just can't believe that I didn't immediately notice that it was a server error and not a vBulletin or PHP error.


All times are GMT -7. The time now is 04:33 AM.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.