|
|
Rank: Member
Groups: Member
Joined: 6/8/2007
Posts: 13
|
I have reviewed many threads and I am still having a problem. The ConvertHtml will not display images and instead it displays a ? in the pdf. The code is: HtmlToPdf.ConvertHtml(genReport, doc); The image html is: <img align="middle" src="https://server/images/forms/Symbiosis/SCHC_Logo.png" alt="SCHC Logo" style="margin-right: 0px" /> I can see this image outside and inside the server. The ConvertHtml does not make a call to the server to get the image (according to "Fiddler"). I have tried the BaseUrl option and it still does not work.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,225
|
Hi, This usually means the client machine can not reach the server machine, for example, "server" on your client machine might point to a computer other than the one that you believe it points to. You can try to replace your image src with some images that are publically on the Internet (for example, you can try our logo https://www.essentialobjects.com/Images/Logo.gif) and see if it works. If that works, then your image Url is wrong. Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/8/2007
Posts: 13
|
I have verified via IE that the image is available both from the machine where the image is and outside the machine. The image does not show up when the ConvertHtml is available. The image is on the same machine as the code
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,225
|
Hi,
Are you using a very old version of EO.Pdf? Try to use http instead of https and see if it works.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/8/2007
Posts: 13
|
Yes, I am using V3.0.52.2. I tested with the http and it does work.
Is there a patch or is my only option upgrade?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,225
|
The root of the problem is the supported TLS version over a SSL connection for the HTTPS request. Your version is very old and it only supports TLS 1.1, which over the year has been deemed outdated and unsafe. As a result, many web servers nowadays are configured to ONLY support TLS 1.2. Because your version of EO.Pdf does not support TLS 1.2, it is unable to establish a SSL connection to the web server that requires TLS 1.2. To resolve the problem, you will need to either upgrade EO.Pdf to current (the current version does support TLS 1.2), or rollback your web server's TLS version from 1.2 to 1.1. Even though technically both options will work for you, obviously for security reason you should consider upgrading EO.Pdf to current instead of downgrading your web server's TLS version.
The newer TLS version support is just one of the numerous improvements the current version has over your version. The current version uses a much newer browser engine --- your version uses an outdated WebKit based browser engine, and the current version uses Google's Chromium browser engine, which is the same browser engine that powers Google Chrome browser and has a much larger user base and is being much more actively developed/maintained. We also regularly sync to the latest Chromium code base to keep it up to date. So there are a lot of benefits to upgrade to the current version. Not to mention that over the years we have received many test cases/files from our users, and as we work through those cases, the product becomes a lot more robust and tolerate.
We provide upgrade discount for orders in the past 3 years --- and the older your order is, the less the discount. Based on the version you provided, you probably have long passed this window. So unfortunately in order to use the current version, you will need to place a brand new order. If you do have a newer order that might qualify you any upgrade discount, please PM us your order number and we will check that for you.
Thanks!
|
|