We have been encountering errors when calling Aspose APIs since this morning.
A sample request URL is:
http://api.aspose.cloud/v3.0/pdf/storage/file/uploaded_xxxxxxxx/Invoice.pdf
This returns a 400 Bad Request error.
In the details section, we can see the following message:
Error: UploadFileAsync. Exception: IDX10503: Signature validation failed.
Could you please investigate and advise on the cause of this issue?
The 400 Bad Request error you are encountering, specifically the message “IDX10503: Signature validation failed,” typically indicates an issue with the authentication process when making requests to the Aspose APIs. Here are some steps you can take to troubleshoot and resolve this issue:
Check Your Credentials: Ensure that you are using the correct API key and App SID. Any discrepancies in these credentials can lead to signature validation failures.
Verify Request Format: Make sure that your request is properly formatted. This includes checking the URL, headers, and body of the request. If you are using a specific library or SDK, ensure that it is up to date and correctly configured.
Use SDKs: If you are not already using it, consider utilizing the Aspose SDKs for your programming language. These SDKs handle authentication and request formatting for you, which can help avoid common pitfalls. For example, the Aspose.Storage Cloud SDK for .NET is recommended for uploading files.
Check for Service Updates: Sometimes, issues can arise due to changes on the server side. It may be worth checking if there have been any recent updates or changes to the Aspose services that could affect your requests.
Review Error Logs: If available, check any error logs or detailed responses from the API to gain more insight into what might be causing the issue.
If the problem persists after following these steps, consider reaching out to Aspose support for further assistance, providing them with the details of your request and the exact error message you are receiving.
For additional context, there have been similar reports of 400 Bad Request errors related to file uploads, which were resolved by ensuring the correct setup and usage of the API [1][2].
Sources:
[1]: Uploading PDF file to Cloud Storage using Aspose.Storage REST API throws Bad request error
[2]: Getting 400 Bad Request from API - Aspose Cloud Forum
We have not made any changes to our code. These API calls have been working reliably for over a year and were functioning correctly until today.
I have updated my SDK to the latest version and still have the same problem . I think there is something wrong on your side.
@conveysoft
Can you please share your sample document and code to reproduce the issue? We will further proceed to assist you accordingly.