seems to not work when ssl is enabled unless you first open sabnzbd in the browser

[GoogleCodeExporter]

seems to not work when ssl is enabled unless you first open sabnzbd in the browser

[GoogleCodeExporter]

Exact same is happening for me on an (untrusted) ssl connection, under Windows 7

Original comment by [email protected] on 25 Apr 2010 at 6:01

[GoogleCodeExporter]

the problem is it's very hard to add an untrusted certificate to chrome as 
trusted, you 
have to download the certificate elsewise and import it into chrome to do it.

the best solution would be to figure out a way for sabconnect to accept 
untrusted certs 
on its own.

for now i'm just using SABSTATUS in firefox, but it sucks having firefox open 
all the 
time just to interface with sabnzbd.

Original comment by [email protected] on 25 Apr 2010 at 6:31

[GoogleCodeExporter]

SABConnect won't be able to allow untrusted HTTPS certificates until the end 
user himself allows it. That's just how Javascript XmlHttpRequests work.
The best way is to import the invalid certificate.
Chrome uses the OS certificate tools, so if you're on Windows simply import the 
certificate using Internet Explorer. This will add the certificate to the 
Windows datastore, and Chrome will see that.
I think it's pretty much the same for OSX, and maybe even Linux.

Original comment by guillaume.boudreau on 29 Jun 2010 at 12:55

[GoogleCodeExporter]

importing an untrusted certificate is not a trivial task in chrome like it is 
in firefox. that solution is not feasible for the majority of the userbase.

Original comment by [email protected] on 29 Jun 2010 at 12:32