The list of hubot adapters in the hubot documentation is being replaced with a link to a GitHub topic search. Add the hubot-adapter topic to your repository on GitHub to include it in this list.

/cc hubotio/hubot#1320

Hi,

I am trying to get this hubot plugin running against a on premise TFS2015.

The authentication and retrieval of user info and rooms is working properly but when hubot tries to connect to a room I get the following error message on the console:

INFO Failed to join room with status 400

I had a look at the server logs, the URI that was requested is ok, but the accept header does not contain the api-version. I used postman to test the url with and without the accept header and if I included it, it worked properly.
The serverlog also shows that the retrieval of users sends the request with the correct accept header. Only the put operation to join a room does not include it (I don't know about others, I can't get further than the joining a room part).

Snipped from the server log:

Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken Content-Type Accept

2015-07-07 16:33:24 10.49.13.227 GET /_apis/chat/rooms - 80 [email protected] 10.49.56.244 vso-client/1.0+node/0.10.25+linux - 200 0 0 21 application/json application/json;+api-version=1.0
2015-07-07 16:33:24 10.49.13.227 GET /_apis/connectionData - 80 [email protected] 10.49.56.244 vso-client/1.0+node/0.10.25+linux - 200 0 0 15 application/json application/json;+api-version=1.0
2015-07-07 16:33:24 10.49.13.227 PUT /_apis/chat/rooms/4/users/cddfa03f-b91f-480d-932e-d5986a69d718 - 80 [email protected] 10.49.56.244 request-json/1.0 - 400 0 0 75 application/json application/json
2015-07-07 16:33:24 10.49.13.227 GET /_apis/chat/rooms/4/users - 80 [email protected] 10.49.56.244 vso-client/1.0+node/0.10.25+linux - 200 0 0 113 application/json application/json;+api-version=1.0

Hubot runs on a Ubuntu machine 14.04
node version: 0.10.25
hubot-vsonline version: 0.2.9 (via npm install)

Any idea how I can get around this issue?