There is nothing in Q2A that produces this response code. So as pupi1985 said it sounds like a server error.
Check with your host in case there is some problem there. We have had problems with the Apache mod_security plugin blocking perfectly legitimate requests because it thought the request was SQL injection.
If you get an answer from your host let me know, we may be able to work around it.