Response differences between FileStore (NS3) and ObjectStore (NS4)

Some differences exist in the response body.

Rely on the response code

While no modification is generally needed to use NS3 API calls with NS4, there are subtle differences in the response body that could impact your workflow. We recommend relying on the response code due to these differences.

Response strings can change

This is not a maintained or exhaustive list of response strings as they are subject to change. Be aware of and avoid using the strings listed below when upgrading from FileStore (NS3) to ObjectStore (NS4):

Call Example differences
Any The Accept-Ranges response doesn't exist for NS3.
  • NS3: N/A
  • NS4: bytes
Any The Server response is different:
  • NS3: Apache
  • NS4: AkamaiNetStorage
Any The Content-Type field is empty for NS4.
  • NS3: text/html
  • NS4:
Any The Content-Length responses are different. A value of 0 is not abnormal for NS4.
  • NS3: '31'
  • NS4: '0'
Any The http_version response is empty for NS3 and null for NS4.
  • NS3:
  • NS4: null

Upload
Response: 200

The String response is empty for NS4.
  • NS3: "<HTML>Request Processed</HTML>\n"
  • NS4: ''

Delete
Response: 200

The String response is different.
  • NS3: "<HTML>Request Processed</HTML>\n"
  • NS4: 'deleted\n'

Delete
Response: 404

The String response is different.
  • NS3: "File not found."
  • NS4: "not found\n"