无法呈现网址。无法从 url 获取图像。导航超时

发布于 2024-11-28 09:54:31 字数 563 浏览 5 评论 0原文

我有一个 ASP.NET Web 应用程序,其中包含 Winnovative HTML 到 PDF 转换器

这已经运行了一年多,成功生成了 PDF,

但是,这不再起作用,返回的错误是:

Could not render the url. Could not get image from url.Navigation timeout..

我已经检查了 Winnovative FAQ,他们建议向 PdfConverter 的实例添加 NavigationTimeout。我添加了以下内容:

PdfConverter.NavigationTimeout = 500

但是,这并没有修复错误。此外,直接在浏览器中加载时,转换的页面只需要几分之一秒的时间即可加载,因此我不认为这是呈现页面的性能问题。

以前有人遇到过这个问题吗?是否有任何已知的解决方案/原因?

I've got a ASP.NET web application which contains the Winnovative HTML to PDF Converter.

This has been running for over a year successfully generating PDFs

However, this is no longer working, and the error being returned is:

Could not render the url. Could not get image from url.Navigation timeout..

I've checked the Winnovative FAQ and they suggest adding a NavigationTimeout to the instance of the PdfConverter. I've added the following:

PdfConverter.NavigationTimeout = 500

However, this has not fixed the error. Furthermore, the page being converted only takes a fraction of a second to load when loading directly in the browser, so I don't believe its a performance issue with the page being rendered.

Has anyone experienced this problem before? Are there any known solutions/causes for this?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

酒中人 2024-12-05 09:54:31

最后我发现发生这个错误是因为我们试图从 HTTPS 文件请求 PDF。

但我无法解决原因。

如果您有答案,请参阅此问题:

从 HTTPS 生成 PDF 会导致错误

In the end I found out this error was occuring because we were trying to request a PDF from a HTTPS file.

I weren't able to solve why though.

Please see this question if you have an answer:

Generating PDF from HTTPS causes error

救星 2024-12-05 09:54:31

如果其他人收到此错误:在我们的示例中,在 IIS 8.5 上运行,将应用程序池从 ApplicationPoolIdentity 更改为 Network Service 修复了该错误。所以看来这是一个文件夹权限问题。网络服务并不理想,实际上应该设置实际的文件夹权限。

If anyone else gets this error: In our case, running on IIS 8.5, changing the application pool from ApplicationPoolIdentity to Network Service fixed it. So it seems it is a folder permission problem. Network service isn't ideal and really the actual folder permissions should be set.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文