Looking at GlassWire for Windows, my BOINC client only connects to WCG via scheduler.worldcommunitygrid.org over 443/tcp (https), but the official WCG URL and Web_URL are still using the antiquated URLs from 2004ish.

(from all_projects_list.xml)
<url>http://www.worldcommunitygrid.org/</url>
<web_url>http://www.worldcommunitygrid.org/</web_url>

(from account_www.worldcommunitygrid.org.xml)
<master_url>http://www.worldcommunitygrid.org/</master_url>

The Rosetta@home project recently changed the project URLs within BOINC to https. Would it be feasible for WCG to do the same? I'm not sure if coordination needs to happen with a new BOINC release (to update all_projects_list.xml) or if any other moving pieces need to be coordinated or if this is simply a matter of communication and execution.

I know far too many mindless corporate InfoSec people who wouldn't hesitate to red light WCG without diving any deeper, even if I "tell" them that all traffic really goes over https only and show them packet captures. They won't care, since all they see is "http."

Is the Level of Effort for such a change request pretty minor? Just curious, as I'd love to see more WCG modernization even if incrementally. Thanks for the consideration!