Nathan,  You have hit a bug with the AtmosFox browser.  It's not properly handling the object with a filename that has been URL encoded.  We're working to get that condition fixed, but don't have an ETA.  You could delete the objects through our API or with another object browser application.  Or you could create another Atmos subtenant through the management interface and just use that with the Riverbed appliance.  Happy to help with either of these options.   Raj
 Hi All,  Fairly new to Atmos, and have been testing out the AiaB and utilising the AtmosFox Explorer initially to test everything is working. The piece of equipment that will actually be reading and writing to Atmos is a Riverbed Whitewater appliance to move optimised backups to the Atmos "cloud".  However when the Whitewater initialises it says the Atmos directory is not empty.  So i took a look and sure enough there was a file in the directory.  I tried deleting it via Fox but got the "there was a mismatch between the signature in the request and the signature computed".  I need to remove this file but nothing seems to work.  I have tried both over HTTP and HTTPs. This is the request : DELETE /rest/namespace/ww-nc-sg/rbt%5Fmdfiles%5Fencrypted HTTP/1.1\r\n which gives : HTTP/1.1 400 Bad Request\\r\\n There was a mismatch between the signature in the request and the signature computed by the server.  And i am sure the UID/secret is correct because i can add and delete other files into that same directory via AtmosFox..  Is there any way of just emptying everything in the namespace for this UID from behind the scenes ?  Or any other suggestions of getting rid of that file. ?  Thanks Nathan
mismatch between the signature in the request and the signature computed