Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • B bjgf
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 127
    • Issues 127
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • BlueJ
  • bjgf
  • Issues
  • #2188
Closed
Open
Issue created Dec 15, 2021 by Neil Brown@nccbMaintainer

BlueJ and Greenfoot contact the server using HTTP

Currently, BlueJ and Greenfoot contact the server for a limited number of reasons:

  • Ping stats.{bluej,greenfoot}.org on load
  • Load bluej.org/version.info to check the latest version
  • Contact greenfoot.org to log in, fetch scenario info and share scenarios

All of this is done via HTTP just because we didn't support HTTPS at the time. These days we should be using HTTPS for these by default. There is also an issue that none of these requests understand redirects (otherwise we could just redirect HTTP to HTTPS server-side); I wonder if that may be possible if we switched to using the Apache web libraries rather than the built-in JDK Connection?

Assignee
Assign to
Time tracking