Currently, the SPARQL endpoint client code assumes HTTP protocol. It ignores HTTPS scheme name in the URI and used HTTP anyway. Clearly, this is not correct behaviour, and can be confusing to boot.
SparqlHttpClient.py currently uses a low-level HTTP connection library that supplies distinct classes for HTTP and HTTPS connections. The documentation (now) recommends use of the higher level "requests" library instead - which I assume would take care of this.
Currently, the SPARQL endpoint client code assumes HTTP protocol. It ignores HTTPS scheme name in the URI and used HTTP anyway. Clearly, this is not correct behaviour, and can be confusing to boot.
SparqlHttpClient.py currently uses a low-level HTTP connection library that supplies distinct classes for HTTP and HTTPS connections. The documentation (now) recommends use of the higher level "requests" library instead - which I assume would take care of this.