Skip to content

Testing: add a regression test that proves ?token= never leaks into access logs #33

@francescobianco

Description

@francescobianco

Summary

There is no automated regression test proving that ?token= is removed from request logs and access-log formatting continues to mask token values. Since the query-token fallback is a key compatibility feature, it deserves a direct check.

Reproduction

  1. Run the server with access logging enabled.
  2. Send requests using ?token=.
  3. Inspect logs manually.
  4. There is currently no automated check guarding this behavior.

Expected

A focused test should assert that token values do not appear in access logs and that the middleware strips the query string before logging.

Actual

This remains a manual assumption.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions