delete() throwing exception on 404 instead of returning false about softlayer-object-storage-php HOT 7 CLOSED

Hello,

As you pointed out 404 response is expected when a DELETE request is performed on an object that doesn't exist. I'd suggest you wrap the delete call with a try/catch block.

The unit test expects the delete operation to be successful. I wanted the test to fail if the delete operation is not successful. Sorry about the confusion though.

Cheers!

from softlayer-object-storage-php.

Thanks for getting back to me and for the confirmation. I went ahead and wrapped the delete call, along with all other calls to ObjectStorage, inside a try/catch block. This way it won't cause a fatal error within my web application. One last question. Once I've caught the 404, or whatever the exception might be, is there a way to get the status code that was received? Something like $e->getStatusCode() where $e is an Exception object?

from softlayer-object-storage-php.

I think the ability to get the HTTP code from an exception is a great idea. I will implement the exception code for all HTTP exception sub classes so you can use $e->getCode(). Also, I will update all ObjectStorage_Exception_Http_* classes to implement ObjectStorage_Exception_Http_Interface so you can expect the HTTP status code when you're catching these exceptions.

from softlayer-object-storage-php.

Wow! That would be very helpful. Thanks! I'll look forward to the update.

from softlayer-object-storage-php.

HTTP exceptions will have the status code now.

Cheers!

from softlayer-object-storage-php.

Probably needs docs in the README

from softlayer-object-storage-php.

Going ahead and closing this since it looks like it was resolved with c65981b. Thanks!

from softlayer-object-storage-php.