Skip to content

403 on whatsdue command #224

@JamesDearlove

Description

@JamesDearlove

This might be an Infra only issue, but it appears we are getting HTTP 403 errors connecting to my.UQ on the whatsdue command. In the past we've set the user-agent to UQCS so we weren't blocked, but that appears to no longer be the case. Good chance we're being blocked based on connections from the public Azure IP space.

Metadata

Metadata

Assignees

No one assigned

    Labels

    infra-onlydue to access requirements (database stuff, usually), only infra can complete this

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions