Skip to content

Add ETag / 304 caching on /api/proxy #780

Description

@greatest0fallt1me

Description

This is a backend issue for the GrantFox FWC26 campaign (Stellar Wave). Emit strong ETags on /api/proxy and honor If-None-Match with 304 to cut bandwidth on repeat reads.

Requirements and Context

  • Implement per the description above
  • Add focused tests for the change
  • Document any API/visible changes
  • Adhere to repo's lint and code style
  • Must be secure, tested, and documented

Suggested Execution

  1. Fork the repo and create a branch
  2. Implement changes:
    • src/routes/proxy.ts
    • src/middleware/etag.ts
  3. Test and commit; open a PR with Closes #780 in the body

Guidelines

  • Minimum 90% test coverage on changed lines
  • Input validation at the boundary; standardized error envelope
  • Structured logging with correlation IDs
  • Clear documentation and inline comments
  • Timeframe: 96 hours

Metadata

Metadata

Assignees

No one assigned

    Labels

    GRANTFOX OSSGrantFox open-source campaign taskMAYBE REWARDEDMay be rewarded under the GrantFox campaignOfficial Campaign | FWC26Official GrantFox FWC26 campaign issueStellar WaveStellar Wave Program issuebackendBackend service work

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions