Yes, when I reenable the option it stops working and yes, the proxy compatibility option is on. Currently, I have Jenkins setup to run behind nginx. Here is some information regarding the request/response:
Headers:
Cache-Control must-revalidate,no-cache,no-store
Connection keep-alive
Content-Encoding gzip
Content-Type text/html;charset=ISO-8859-1
Date Mon, 13 Oct 2014 00:27:09 GMT
Server nginx/1.6.2
Transfer-Encoding chunked
view source
.crumb e537ac28fab87ecb9a9319aaf5bc193b
Accept text/javascript, text/html, application/xml, text/xml, /
Accept-Encoding gzip, deflate
Accept-Language en-US,en;q=0.5
Cache-Control no-cache
Connection keep-alive
Content-Length 0
Content-Type application/x-www-form-urlencoded; charset=UTF-8
Cookie JSESSIONID.bae0ecf2=mk3f6tod1v51fh5xb4xbgm5c; screenResolution=1440x900
Host jenkins.fountain.com
Pragma no-cache
Referer https://jenkins.fountain.com/job/Build/
User-Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0
X-Prototype-Version 1.7
X-Requested-With XMLHttpRequest
Response:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 403 No valid crumb was included in the request</title>
</head>
<body><h2>HTTP ERROR 403</h2>
<p>Problem accessing /job/Build/build. Reason:
<pre> No valid crumb was included in the request</pre></p><hr /><i><small>Powered by Jetty://</small></i><br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
</body>
</html>
Please explain in more detail what behavior you're seeing. How you are scheduling builds? What is supposed to happen, what actually happens? Are queue items created? If so, what is the reason they're not getting scheduled?