PDF Output Error

Using SC 8.1 I created a very plain grid deployed to a very basic, established CentOS/Apache server with proper ssl certs. The deployed grid works great except when I export out to PDF. What I get is a 404 screen indicating a missing html file, which was created during the wkhtmltopdf creation process. Initial indication is that the grid is trying to send the browser to http, instead of https. I have deployed other grids without this issue using SC 7x. When I compare the code generated between the two versions of SC I find one difference, the SC8.1 code contains the following line in the index.php file, while the index.php file generated from the SC7x does not contain the following line:

$arq_pdf_in = str_replace(“https://”, “http://”, $arq_pdf_in); $arq_pdf_in = str_replace(“https://”, “http://”, $arq_pdf_in);

If I switch the position of the https and the http terms in this line of code or if I remark out this line of code totally, the PDF generation works entirely. I have searched all settings within SC, this forum and documentation regarding wkhtmltopdf and cannot find how this is happening. I really need the PDF generation working entirely for my current project, and I really don’t want to change this manually for obvious reasons. Does anyone have any ideas I could try to solve this? Thanks!

The only solution I’ve found is to have the same web server allow connections to http as well as https.
You can protect the web server by setting an ACL in its web config, to allow http only from localhost (this is possible with apache so I guess all\most web severs can do that).

I have posted the same thing in another forum in Spanish, I use Windows 2012 server and Apache Server, but unfortunately NETMAKE does not seem to read or have enough moderators to answer us.

I have been able to check how to change the version of wkhtmltopdf (Scriptcase 8.1 continues in the obsolete version 0.10.0_rc2), any one higher than 0.10.0_rc2 works !, but the report comes out either with the smaller letter, or with fewer lines by page. In other words, it works poorly.

This happens because internally we have not changed the commands that the version 0.10.0_rc2 uses and to handle the conversion from html to pdf they do not adapt properly when using another more modern version. For example when defining the lines per page, namely how to pass this Scriptcase information to wkhtmltopdf.

Only NETMAKE can modify the software that handles wkhtmltopdf internally use or not the oldest or most modern version 0.12.4 of November 22, 2016.

In the meantime we can not use HTTPS in our information systems.

We will continue to await a reply.

Regards

kriptonita