Mike Raineri

I'll try to think of ways to work around this. Nothing obvious comes to mind at this moment without performing additional GET operations to inspect version numbers and the vendor...

Currently that's not really possible. We could accommodate having the tool send a multipart request for something like an operation to the UpdateService when trying to perform an update, but...

Is there an exception shown from the sample that could be shared? I would like to see where exactly the timeouts are coming from. Can you also try changing "session"...

Are your proxy settings configured via the following environment variables like this, or is there something else your browser is using? ``` export HTTP_PROXY="http://192.168.1.10:8888" export HTTPS_PROXY="http://192.168.1.10:8888" ```

No, installing a certificate isn't needed for the interface to work (but it is encouraged since most services come with a self-signed certificate by default). At least from the messages...

The library itself doesn't contain that level of logic; it stops at producing a Python dictionary from the the JSON response, and leaves it up to the caller to extract...

You need to specify the scheme with the address; instead of `--rhost 10.250.2.2` it should be `--rhost http://10.250.2.2` Probably worth adding some validation in the library to make the exception...

It's hard to tell without the payload in question, but it appears the service is not rendering the mandatory `@odata.id` property in one or more of its Drive resources. If...

It could be that there was an error in getting the resource in question (and error payloads do not have `@odata.id` properties). This might be a good time for me...

You should be able to get it from a browser and paste it here. From the trace, it's following the links through Systems, Storage, and Drives. Depending on the number...