scaeloutSean

That sounds possible, @gaffneyd4. Mine is also "behind", but it's hard to know for sure since we couldn't try the other scenario. But being behind and trying to find an...

> In theory the app should be treating that file as text not a blob. I don't have `locks/*` in my bucket, but here's an example for another JSON file...

I wouldn't force path-style URLs on all S3 implementations without a switch/option, as most implementations [can](https://stackoverflow.com/questions/59693471/how-to-setup-minio-server-to-use-virtual-hosted-style) do both.

Of course, since `sfe.list_volumes()` and other methods work correctly prior to `.to_json()`, a workaround is to convert to JSON by yourself.

Forgot to mention in the case somebody comes across this before it's fixed: the old "invoke" workaround still works fine. `{"volume_ids": [1]}` has no effect, all volumes' QoS histograms get...

Doh... Should be `VolumeIDs`, not `volumeIDs`... ```json { "method": "ListVolumeQoSHistograms", "params": { "VolumeIDs": [134] }, "id": 1 } ```

Check your user's ~/.netapp_dataops/config.json and adjust if necessary. (My config works with both `false` and `true` in s3VerifySSLCert.) ```json { "verifySSLCert": false, "s3Endpoint": "https://s3.com.org.net:443", "s3AccessKeyId": "AAAAAAAAAAAAAAA", "s3SecretAccessKey": "BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB", "s3VerifySSLCert": true,...