Today we have enabled SSL for Queryfeed. Now, all the data moving from Queryfeed to you is encrypted. That is quite important that nobody cannot read it except you. Nowadays, SSL is highly recommended by Google, Mozilla and other companies. More and more sites on the Internet start using SSL instead of usual insecure method and Queryfeed follows that trend.

You can easily check if the site you have visited supports secure connection by the green label in the URL bar: SSL proof

Technical notes

Using SSL means that all the URLs start from https://, not http://. If you call the old URL started from http://..., Queryfeed will redirect you to the same URL with the https://... scheme. Most of HTTP client libraries follow redirects automatically. Let’s try to call some query through Python:

1
2
3
4
5
6
7
8
9
10
11
12
13
import requests

res = requests.get("http://queryfeed.net/twitter?q=test")
res.status_code
>>> 200
res.content
>>> '<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"...'

res.history
>>> [<Response [301]>]

res.history[0].content
>>> '<html>\r\n<head><title>301 Moved Permanently...'

This example shows how to call Queryfeed with the Requests Python library. The res.history field keeps the chain of redirects occurred before the final response. As you can see, because of http:// instead of https:// in the URL there were two requests, not one. So if you are interested in performance, pass https://... into your code.

If you are using cURL, you might have the following situation:

1
2
3
4
5
6
7
8
curl "http://queryfeed.net/twitter?q=foo"
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.1.19</center>
</body>
</html>

That’s because cURL doesn’t follow redirects by default. Please correct the URL scheme to https:// or pass the -L flag (that means to follow the Location header):

1
2
3
4
5
curl -L "http://queryfeed.net/twitter?q=foo"
<?xml version="1.0" encoding="UTF-8"?><rss version="2.0">
  <channel>
    <title>Queryfeed | foo</title>
...

We hope this material was useful. If you still have any problems accessing Queryfeed through secure connection, contact us by the email located in the footer below.