Skip to content

Server: missing /Upgrade/Report route causes 404 during silent update #71

Closed

Description

@JusterZhu

Describe the bug

The server registers both URL variants for Verification:

  • /Upgrade/Verification
  • /Update/Verification

But only one variant for Report:

  • /Update/Report

When a client uses the /Upgrade/* URL convention (e.g., http://localhost:5000/Upgrade/Report), the report endpoint returns 404.

To Reproduce

  1. Start the sample server
  2. Run any client configured with reportUrl = "http://localhost:5000/Upgrade/Report"
  3. Observe 404 errors during update status reporting

Expected behavior

/Upgrade/Report should work the same as /Update/Report, mirroring the Verification endpoint pattern.

Fix

See PR

Activity

  1. JusterZhu commented on Jun 3, 2026

    @JusterZhu
    CollaboratorAuthor

    Fixed: the /Upgrade/Report route has been added to Server's Program.cs via PR #43. Both /Upgrade/Report and /Update/Report are now registered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions