Page MenuHomePhabricator

"Home" link of AWMD stats tool (sometimes) uses HTTP [Not Secure] protocol instead of HTTPS
Closed, ResolvedPublic

Description

This task is about a tool at https://tools.wmflabs.org/awmd-stats/ running on Toolforge:

Clicking on the "Home" link

Screen Shot 2018-08-22 at 20.53.56.png (62×113 px, 7 KB)
of the AWMD stats tool sometimes sends an HTTP request to Toolforge instead of an HTTPS. This should be fixed, it's just a tweak on the base template sending the request so it always uses the HTTPS protocol.

Expected

Screen Shot 2018-08-22 at 20.54.13.png (38×402 px, 13 KB)

Actual (sometimes)

Screen Shot 2018-09-20 at 21.27.17.png (55×478 px, 14 KB)

Developer Notes

Work should be done on the base template and running the tool on deployment can be found on the README.md file.

Event Timeline

xSavitar renamed this task from "Home" link of AWMD stats tool links to HTTP version of site instead of HTTPS to "Home" link of AWMD stats tool (sometimes) uses HTTP [Not Secure] protocol instead of HTTPS.Aug 22 2018, 7:59 PM
Aklapper updated the task description. (Show Details)
Kizule added a subscriber: Kizule.

I think to I can fix this. I claimed task on Google-Code-in-2018.

Change 469893 had a related patch set uploaded (by Zoranzoki21; owner: Zoranzoki21):
[labs/tools/awmd-stats@master] Fix linking "Home" to HTTPS

https://gerrit.wikimedia.org/r/469893

Change 469893 abandoned by Zoranzoki21:
Fix linking "Home" to HTTPS

https://gerrit.wikimedia.org/r/469893

Kizule removed projects: Patch-For-Review, User-Kizule.
Kizule removed a subscriber: Kizule.

Change 470250 had a related patch set uploaded (by Nathan fraignt; owner: Nathan fraignt):
[labs/tools/awmd-stats@master] Fix home link not using https

https://gerrit.wikimedia.org/r/470250

Change 470250 merged by jenkins-bot:
[labs/tools/awmd-stats@master] Fix 'Home' link not using HTTPS protocol

https://gerrit.wikimedia.org/r/470250

xSavitar assigned this task to Nathan_fraignt.

Thanks for working on this! Will resolve this and if it happens in the future (after deployment), we'll reopen :)