Hi,
I have images hosted on a local web server using a self-signed certificate. For example:
https://localhost/images/.../file.png
When using ConTeXt, the image cannot be retrieved; a verified signed certificate works as expected.
Using wget, self-signed certificates can be forced:
wget --no-check-certificate https://localhost/images/.../file.png
Does ConTeXt have a way to ignore/bypass certificate validation? If so, how?
(Note: the certificate's common name is currently blank, which does not match 'localhost' -- I can fix that if required...)
Thank you!
On 3/30/2014 5:12 AM, Thangalin wrote:
Hi,
I have images hosted on a local web server using a self-signed certificate. For example:
https://localhost/images/.../file.png
When using ConTeXt, the image cannot be retrieved; a verified signed certificate works as expected.
Using wget, self-signed certificates can be forced:
wget --no-check-certificate https://localhost/images/.../file.png
Does ConTeXt have a way to ignore/bypass certificate validation? If so, how?
(Note: the certificate's common name is currently blank, which does not match 'localhost' -- I can fix that if required...)
a test:
in data-sch.lua you can find:
local function runcurl(name,cachename) -- we use sockets instead or the curl library when possible local command = "curl --silent --create-dirs --output " .. cachename .. " " .. name os.spawn(command) end
you can try to add an option there, remake the format and see if that works i can see if we can add such an option (by default or setup)
Hans
Hi,
Adding --insecure works. I think the option should be present by default, which could save people time trying to understand what part of the system is preventing the images from being downloaded. (For example, for me I first checked caching, directory permissions, web server configuration, and the wiki before posting to the list.)