With BuildTokenRoot 1.1, I was triggering jobs with a URL and getting 200 with no problems at all. Here's a sample Nginx log:

aaa.bbb.ccc.ddd - - [06/Sep/2015:18:35:42 +0300] "GET /buildByToken/build?job=xxxxx&token=yyyyyyy HTTP/1.0" 200 11 "-" "-" "-" 

After I upgraded to 1.3, I'm getting this:

aaa.bbb.ccc.ddd - - [06/Sep/2015:17:28:43 +0300] "GET /buildByToken/build?job=xxxxx&token=yyyyyy HTTP/1.0" 201 0 "-" "-" "-" 
aaa.bbb.ccc.ddd - - [06/Sep/2015:17:28:43 +0300] "GET /queue/item/81/ HTTP/1.0" 403 833 "-" "-" "-" 

The "queue item url" feature introduced in 1.3, causes my client to request it and the client gets a 403 Forbidden error since it doesn't have permission to access it.

Is it possible to make this "queue item url" feature optional? We can give an additional parameter like:

/buildByToken/build?job=xxxxx&token=yyyyyyy&give_queue_item=1