update print to python 3 and schema to https

[gkesaev]

No description provided.

[idanmel]

Thanks for the pull request.
We allow http requests to our API.

Can you please change the schema back to http?

[gkesaev]

No worries.
To be clear the only reason for this pull request is http schema.
If you like I can change it so the user would have the option to choose http/s but truly I think that this is a bad idea.
One might use this library for the first time without checking exactly what the code does and use it to search for some very sensitive information over say cyber API.
What do you think?

[idanmel]

Hi Nescobar,
That's a good idea.
Maybe have HTTPS as the default, and give the user the option of using HTTP?

[gkesaev]

@idanmel I've thought about it and I think that there is no point in leaving the HTTP schema.
With the provided services your customers may search for very sensitive data, and some of them are probably doing it right now over the clear web.
I think it should be the other way around: you should help your users by enforcing them to use a more secure connection and if someone wants they'll be able to downgrade to HTTP after changing one line of code.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information