You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while testing the download feature of the REST server part, I figured the aasx file is somehow rebuilt for download. At least the xml part is rewritten.
This will fail, if a signed aasx file is downloaded, since the signature verification of the downloaded file will most likely fail (except for the case the rebuilt xml matches exactly the original one). Also, it simply seems odd the downloaded file does not match the original one.
I suggest, the download endpoint should just take the aasx file from the input folder and send it to the client as is.
The text was updated successfully, but these errors were encountered:
This issue has been fixed in the new REST API support with ASP.NET.
The new REST endpoint is : http:// <Host_Name> :5001/
Swagger documentation for these APIs can be found at : http://<Host_Name>:5001/swagger/index.html
Package explorer can be connected to Aasx-Server by: File -> AASX File Repository -> Connect HTTP/REST Repository and appending "?asp.net" to the new REST endoint as shown in the screenshot.
Hi,
while testing the download feature of the REST server part, I figured the aasx file is somehow rebuilt for download. At least the xml part is rewritten.
This will fail, if a signed aasx file is downloaded, since the signature verification of the downloaded file will most likely fail (except for the case the rebuilt xml matches exactly the original one). Also, it simply seems odd the downloaded file does not match the original one.
I suggest, the download endpoint should just take the aasx file from the input folder and send it to the client as is.
The text was updated successfully, but these errors were encountered: