All methods which deal with storage - lockerGet, lockerPut, etc - return HTTP headers to denote success or failure. The two important headers are "X-MP3tunes-ErrorNo" and "X-MP3tunes-ErrorString".
Response Headers
X-MP3tunes-ErrorNo: 200001
X-MP3tunes-ErrorString: Request Successful
X-MP3tunes-ErrorNo: 400002
X-MP3tunes-ErrorString: File identification error
Files in Oboe storage are identified by unique file keys, generated from the hash of the content of files. When a file is sent to MP3tunes for storage, the file key (the hash of the content of the file) is sent along with it. This error occurs when the MD5 hash used for a file key is calculated on the server and does not match what was sent up with the file.
X-MP3tunes-ErrorNo: 401001
X-MP3tunes-ErrorString: Authentication Error
This error occurs when there is an attempt to use a session which has expired on the server. If this occurs, call the login method to retrieve a new session id.
X-MP3tunes-ErrorNo: 403001
X-MP3tunes-ErrorString: Empty File Error
This error occurs when a file sent to MP3tunes for storage is zero bytes in length.
X-MP3tunes-ErrorNo: 404001
X-MP3tunes-ErrorString: File Not Found Error
This error occurs when a file is requested from storage which no longer exists.
X-MP3tunes-ErrorNo: 409001
X-MP3tunes-ErrorString: CRC Error
In order to identify actual file key mismatch errors a CRC is used to identify data loss or corruption when a file is transfered over a network for storage. This way if a file is corrupted while uploading another attempt can be made.
X-MP3tunes-ErrorNo: 413001
X-MP3tunes-ErrorString: File Too Large Error
Although there is no overall size limitation for an MP3tunes Oboe locker, there is a limit of 20 Megabytes per file.
X-MP3tunes-ErrorNo: 415001
X-MP3tunes-ErrorString: File Format Not Supported Error
Some file formats, such as FLAC and ALAC, are not supported at this time.
X-MP3tunes-ErrorNo: 500001
X-MP3tunes-ErrorString: Storage Subsystem Error
This error occurs when there is a problem with our storage system.