Hello Essential Objects Team,
We are currently testing our application running in an AWS container using a Windows Server 2022 (Full) Windows container. We are using EO.Pdf version 24.2.81.0.
When exporting HTML to PDF, we encounter the following exception when font styling is present:
`HtmlToPdfException: The request was canceled`
We have confirmed that:
* Exporting very simple HTML without font styling succeeds
* Adding font styling causes the request to be canceled
* This behavior closely matches the issue described in the following forum post from 2023:
https://www.essentialobjects.com/forum/postst11598_EOPdf-20025-The-request-was-canceled-error.aspxIn our container environment, standard system fonts such as Arial and Segoe UI are not present by default, and we have not found a Microsoft-supported, container-safe way to reliably restore those fonts at image build time. We understand that previous guidance referenced installing fonts on the server, but this is not trivial in Windows container environments.
Our questions are:
1. Has this issue been addressed or improved in more recent versions of EO.Pdf (post‑2023)?
2. Is installing system fonts still the recommended solution in containerized Windows environments?
3. Does EO.Pdf officially support Windows containers, and if so, is there guidance or configuration recommended to avoid this font-related failure?
4. Are there alternatives supported by EO.Pdf (e.g., embedded fonts, different rendering options, or configuration flags) that avoid relying on OS-installed fonts?
Any guidance on supported approaches for running EO.Pdf in Windows containers would be greatly appreciated.
Thank you for your time and assistance.
Best regards,
RM