I'm guessing this would break existing configurations. (Or we could detect if the endpoint contains the schema and prepend https:// only if it doesn't - for backwards compatibility).