HTTPS in derived links

While reviewing issues with an SGF downloader, I noticed that all HTTP is getting redirected to HTTPS.

This is fine, but the next and previous links in the JSON returned point to HTTP URLs. This causes extra requests to the server.

Shouldn’t these links be modified to provide HTTPS in the returned URLs used for navigation?

One example is the games list when requested as JSON:

{"count": 944, "next": "http://online-go.com/api/v1/players/1707/games/?page=5&format=json", "previous": "http://online-go.com/api/v1/players/1707/games/?page=3&format=json",...

This even happens when requested directly as HTTPS. The only difference is the avoidance of the 301 redirect.

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.