Free Support Forum - aspose.cloud

Word Document Manipulation RESTFul API Aspose.Words Cloud returns unsecured URLs in response

Hi,

The words API v4 is returning relative links which are HTTP not HTTPS, yet the Aspose API is not accessible over HTTP. This means to use any of the links we have to convert them to HTTPS, which is cumbersome when using the API programatically.

Aside from this, the “RenderLinks” returned by the API do not do anything, I’m not clear about what they are meant to do?

{
"DrawingObject": {
"RenderLinks": [
  {
    "Href": "http://api.aspose.cloud/v4.0/words/testDocument.docx/sections/0/headersfooters/2/paragraphs/0/drawingObjects/0?format=jpeg",
    "Rel": "self"
  },
  {
    "Href": "http://api.aspose.cloud/v4.0/words/testDocument.docx/sections/0/headersfooters/2/paragraphs/0/drawingObjects/0?format=tiff",
    "Rel": "self"
  },
  {
    "Href": "http://api.aspose.cloud/v4.0/words/testDocument.docx/sections/0/headersfooters/2/paragraphs/0/drawingObjects/0?format=png",
    "Rel": "self"
  },
  {
    "Href": "http://api.aspose.cloud/v4.0/words/testDocument.docx/sections/0/headersfooters/2/paragraphs/0/drawingObjects/0?format=bmp",
    "Rel": "self"
  }
],
"Width": 598.67716535433067,
"Height": 168.66141732283464,
"ImageDataLink": {
  "Href": "http://api.aspose.cloud/v4.0/words/testDocument.docx/sections/0/headersfooters/2/paragraphs/0/drawingObjects/0/ImageData",
  "Rel": "self"
},
"RelativeHorizontalPosition": "Page",
"Left": 0.0,
"RelativeVerticalPosition": "Page",
"Top": 0.0,
"WrapType": "None",
"NodeId": "0.2.0.0",
"link": {
  "Href": "http://api.aspose.cloud/v4.0/words/testDocument.docx/sections/0/headersfooters/2/paragraphs/0/drawingObjects/0",
  "Rel": "self"
}
},
"RequestId": "Root=1-5e8327d4-0e032f9c8dc2a0425e0530de"
}

@RBIEGTechTeam

Thanks for your inquiry. We have logged a ticket WORDSCLOUD-1129 in our issue tracking system after initial investigation. We will keep you updated about the issue resolution progress within this forum thread.

@RBIEGTechTeam

Thanks for your patience. We have resolved your above reported issue in Aspose.Words Cloud 20.4 and also pushed to production. Please try latest version for the fix.