google-code-export / candydolldb

Automatically exported from code.google.com/p/candydolldb
0 stars 0 forks source link

Errors when using https #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Configure Apache to use https in stead of http
2.
3.

What is the expected output? What do you see instead?
The download_image.php does not load the jquery-1.7.2.min.js from it's site, as 
it's trying to access it via https, but the certificate of that site is not 
valid for the used URL.

What version of the product are you using? On what operating system?
I tried the stable and the latest SVN, my used browser is Google Chrome, but I 
also tried it on Mozilla Firefox, which gave the same error.

Please provide any additional information below.
I downloaded the jquery-1.7.2.min.js file, placed it in the /js directory, and 
edited class.html.php to use the local file in stead. Now it works like a charm 
:)

Original issue reported on code.google.com by lenna...@gmail.com on 10 Apr 2012 at 7:27

GoogleCodeExporter commented 9 years ago
Thank you for reporting this issue and pointing to a solution.

We'll take it up immediately :-)

FWieP

Original comment by fwp...@gmail.com on 10 Apr 2012 at 7:33

GoogleCodeExporter commented 9 years ago
The issue has been fixed in r430.

I built in the HTTP(S) switch at the time, but never doubted that the file was 
actually there via HTTPS. Well, it apparently was not :-)

@Developers: Should we include the jQuery js-file statically, as opposed to 
fetching it via HTTP(s)? Since Google does not offer a 'latest' version, we 
might as well. What do you think?

Kind regards,
FWieP

Original comment by fwp...@gmail.com on 10 Apr 2012 at 7:59

GoogleCodeExporter commented 9 years ago
Depending on how often the jquery is updated we could just download and link it 
like you did

Original comment by mranimos...@gmail.com on 10 Apr 2012 at 8:16

GoogleCodeExporter commented 9 years ago
Fetching it via http(s) will cause issues at any rate.... https doesn't work, 
and if using http, you get errors that part of the page is 'not https', so I 
would say to include it statically. Besides that. It's not a 100% necessity to 
have the latest version at all times right?
If it works.. It works?

Original comment by lenna...@gmail.com on 11 Apr 2012 at 2:49