> That would be an incorrectly configured http server. Not wordpress.

Nah, it's WordPress, or more specifically: the sorry state of its community plugins.