Since I'm an indie developer, it doesn't look like I'll be getting my hands on an API key any time soon. I found the Hub whitesheets (2242-222dev-062013-en.pdf) and it looks as though I should be able to interact with the Hub in somewhat similar way as the PLM I was using before, but I'm not seeing anything specific in regards to how to get the Hub to respond by direct http traffic. I would expect simply typing http://192.168.xxx.xxx/buffstatus.xml into the address bar of my browser to return the buffer, but it doesn't connect. Does it only respond to POST requests? Required authentication in the headers? Or is this not supported in the Hub2 anymore?
-
-
It looks like your buffstatus URL is missing the hub's port number after the IP address. The hub's default port number is 25105 so normally the URL would look like this: http://192.168.xxx.xxx:25105/buffstatus.xml -
Ah, masterful! I think the documentation bypassed all that completely. For anyone else who stumbles across this problem, in addition to adding the port, I also needed to provide Basic Authentication with the credentials on the bottom of the Hub, it responded to GET just fine. This worked:
curl -u hubUserID:hubPassword http://192.168.xxx.xxx:25105/buffstatus.xmlComment
-
I don't think this works anymore with Hub FW 1018. I'm getting
→ curl -u xxx:xxx http://192.168.0.x:25105/buffstatus.xml
401 Unauthorized: Password required
Using Postman also gave me same result
POST /buffstatus.xml HTTP/1.1
Authorization: Basic <base64 encoded auth>
401 Unauthorized: Password required
Last edited by brandt; 12-28-2019, 12:04 PM.Comment
-
What are the default credentials on a 2242-222? 2245-222 has a sticker on bottom with them. 2242.222 does notComment
Comment