Verified moved its filestore provider from CityNetwork to Amazon Web Services 21st December 2018.
We have noticed that some of our API users from time to time are having issues with uploading files to AWS.
These are the changes you should be aware of:
1. Do not send the Verified Authorization header to the file store, this will return an error from AWS. In general, access tokens should not be sent to any third party domain.
1. Do not send the Verified Authorization header to the file store, this will return an error from AWS. In general, access tokens should not be sent to any third party domain.
2. You must include a Content-Type header in the upload request.
3. The Content-Type header should not include a charset.
.NET users have reported that some methods in popular httpclient packages don't fulfill AWS' requirements. If you're in this situation, take a look at this example app in C# for uploading files after the migration.
Comments
0 comments
Please sign in to leave a comment.