Getting Bad request error on V1.1 while downloading the file

Aspose.Words Cloud Product Family
1

We are getting Bad request error while downloading the file after successful merge.
[Status=Bad Request, StatusCode=400].

1. We are able to successfully upload the file with below request/response:
System.HttpRequest[Endpoint=https://api.aspose.com/v1.1/storage/file/Speaker%20Bureau%20Unbranded%20Live%20Invitation.docx?&appSID=2f3fe649-546e-4cd1-95b5-009599a1c182&signature=e1SENDOweQy8mLZUUyqGH9nBRw8, Method=PUT]
|CALLOUT_RESPONSE|[147]|System.HttpResponse[Status=OK, StatusCode=200]

2. ExecuteTemplate callout is working fine with below request/response:
|System.HttpRequest[Endpoint=https://api.aspose.com/v1.1/words/Speaker%20Bureau%20Unbranded%20Live%20Invitation.docx/executeTemplate?cleanup=ContainingFields,EmptyParagraphs,UnusedFields,UnusedRegions,RemoveTitleRow,RemoveTitleRowInInnerTables&appSID=2f3fe649-546e-4cd1-95b5-009599a1c182&signature=ZSXNwbhOhQgt8YBrGy9VhpZfueY, Method=POST]
|CALLOUT_RESPONSE|[71]|System.HttpResponse[Status=OK, StatusCode=200]

3. “Getting BAD REQUEST Error while downloading the file with below request/resp”
System.HttpRequest[Endpoint=https://api.aspose.com/v1.1/words/Speaker%20Bureau%20Unbranded%20Live%20Invitation.64637824-804e-48a9-8b51-1336d5c6aa6b.docx?fontsLocation=CustomFonts&format=pdf&appSID=2f3fe649-546e-4cd1-95b5-009599a1c182&signature=DTmNPLN8%2FaNhuEtOtTNsFnWnfW0, Method=GET]
|CALLOUT_RESPONSE|[92]|System.HttpResponse[Status=Bad Request, StatusCode=400]

Can you please look into this on priority as multiple clients are impacted because of this issue.

2

@centris.aspose

The “400 Bad Request” error you are encountering while trying to download the file could be due to several reasons. Here are some steps you can take to troubleshoot and resolve the issue:

  1. Check the URL: Ensure that the URL you are using to download the file is correctly formatted. Look for any illegal characters or encoding issues in the URL.

  2. File Existence: Verify that the file you are trying to download actually exists on the server. If the file was not created or was deleted after the merge, you will receive a 400 error.

  3. File Size Limit: If the file you are trying to download is too large, it may exceed the server’s limits. Check if there are any restrictions on file sizes for downloads.

  4. Clear Cache and Cookies: Sometimes, corrupted cache or cookies can lead to issues. Try clearing your browser’s cache and cookies, then attempt the download again.

  5. Check for Invalid HTTP Headers: If your request includes custom headers, ensure they are valid and correctly formatted.

  6. Test with a Smaller File: If possible, try downloading a smaller file to see if the issue persists. This can help determine if the problem is related to file size.

If you continue to experience issues, consider reaching out to Aspose support for further assistance, as they may have more specific insights into the problem.

3

I asked the responsible team to check what I found in the logs. A couple of times, you get 400 on mailmerge because of a validation issue, etc. But the download method fails with a “Task was canceled exception”, I asked them to check it asap.

4

@yaroslaw.ekimov

Please find the logs for additional last 2 steps that are happening after the 3rd step shared in earlier comment:

System.HttpRequest[Endpoint=https://api.aspose.com/v1.1/storage/file/Speaker%20Bureau%20Unbranded%20Live%20Invitation.64637824-804e-48a9-8b51-1336d5c6aa6b.docx?&appSID=2f3fe649-546e-4cd1-95b5-009599a1c182&signature=b2TpK8Enzv1hvBYKbKlUyU%2BPFDQ, Method=DELETE]
|CALLOUT_RESPONSE|[114]|System.HttpResponse[Status=OK, StatusCode=200]

System.HttpRequest[Endpoint=https://api.aspose.com/v1.1/storage/file/Speaker%20Bureau%20Unbranded%20Live%20Invitation.docx?&appSID=2f3fe649-546e-4cd1-95b5-009599a1c182&signature=e1SENDOweQy8mLZUUyqGH9nBRw8, Method=DELETE]
|CALLOUT_RESPONSE|[114]|System.HttpResponse[Status=OK, StatusCode=200]

Please look into this issue on priority and let us now the ETA for the issue.

5

I already checked the logs by the appsid and shared the information with the storage team, as it seems for some reason a timeout exception is thrown on some calls.

6

@yaroslaw.ekimov

We are getting this issue consistently on every Aspose V1.1 download Api callout request, for multiple clients.

7

I escalated this issue to the team responsible.

8

@yaroslaw.ekimov

Do you have any update on RCA?

9

They rebooted the service, but are still investigating the issue