Problems on Windows

[xogeny]

It turns out that accessing SSL resources on modelica.org programmatically is a problem on Windows. Apparently, there is some known issue with using SSL on Windows.

That link includes a solution which I incorporated into load.py, but haven't tested sufficiently.

[xogeny]

Great. I implemented the "fix", but it turns out that wasn't the problem. Consider the following code:

$ python
>>> import urllib2
>>> req = urllib2.Request("https://encrypted.google.com/")
>>> resp = urllib2.urlopen(req)
>>> x = resp.read()
>>> req = urllib2.Request("https://modelica.org/")
>>> resp = urllib2.urlopen(req)
ssl.SSLError: ...

I strongly suspect that the issue is THE CERTIFICATE on modelica.org. :-(

[dietmarw]

Very strange that that tests works fine on Linux :-(

[xogeny]

The question is, what are we going to do about it? Can we make the index available via a non-SSL connection? There is nothing sensitive in the file so that is an easy solution (assuming the Apache configuration is amenable to it).

[dietmarw]

I searched a bit and came across this: jjlee/mechanize#85 (comment)

Maybe we could implement a similar ssl2 fall-back solution.

[xogeny]

Possibly. But I think making the impact.modelica.org domain support HTTP would be simpler...

[dietmarw]

But this would only fix our repo. What if people start having self-hosted package_data.json files which then would lead to a similar issue. That's why I think we should fix it on the impact side not on the server side.

[dietmarw]

BTW, when working with #61 I had no problems using impact on windows (Win7 64bit). When exactly does the problem occur?

[dietmarw]

Closing this as we no longer develop the python version. The go implementation does not have this issue.