Wrong REST API endpoint/url generation
Posted: Thu Aug 12, 2021 5:10 am
Hi Team
We are using the DocuVieware July 2021 version for the ASP.NET framework 4.8 MVC views.
It is hosted within the Azure app service container. The HTTPS/SSL is terminated at the Azure side.
The problem is DocuVieware is internally generating the REST path dvapi3/docuvieware3api Url.
1.It is accessed via the HTTP protocol instead of the HTTPS protocol.
Wrong Url http://XXXXxx.azurewebsites.net/dvapi3/ ... erequest/1
Correct Url https://XXXXxx.azurewebsites.net/dvapi3/docuvieware3api/baserequest/1
2. The same application is accessed by multiple domains names (hostnames). These names are accessible via the X-Forwarded-Host header
So the document viewer API calls are blocked by the browsers and the document never loads in the browser.
Possible solution. While generating the URL please honor the X-Forwarded-Proto and X-Forwarded-Host headers while generating the URLs
Is there any workaround already exists for this issue?
We are using the DocuVieware July 2021 version for the ASP.NET framework 4.8 MVC views.
It is hosted within the Azure app service container. The HTTPS/SSL is terminated at the Azure side.
The problem is DocuVieware is internally generating the REST path dvapi3/docuvieware3api Url.
1.It is accessed via the HTTP protocol instead of the HTTPS protocol.
Wrong Url http://XXXXxx.azurewebsites.net/dvapi3/ ... erequest/1
Correct Url https://XXXXxx.azurewebsites.net/dvapi3/docuvieware3api/baserequest/1
2. The same application is accessed by multiple domains names (hostnames). These names are accessible via the X-Forwarded-Host header
So the document viewer API calls are blocked by the browsers and the document never loads in the browser.
Possible solution. While generating the URL please honor the X-Forwarded-Proto and X-Forwarded-Host headers while generating the URLs
Is there any workaround already exists for this issue?