Comment 9 for bug 811044

Hi James
I got an email after a post I made on the jenkins mailing list:
"
Do you have CSRF protection enabled? If you do, you need to request a crumb
from the server first, and include that as part of your POST request.

The instructions for how to do this need to be split out into its own page,
but you can find it in the "CSRF Protection" section here:

https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs
"

I did indeed have CSRF protection enabled which might explain why I was seeing the problem and you weren't. (As it happens, this Jenkins instance is only available on an internal company network, so CSRF protection is probably a bit overkill).

I haven't got an explanation as to why things still work if you use a GET request not POST - this would seem to be a hole in the CSRF protection?!

Anyway this sort of explains what was going on.

Tom