Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Legacy SSE GET ignores resolveAuthorizationContext expiresAt

Open Beginner friendly
  • Is something wrong?
#336 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@mcollina is already working on this.

Since Oct 19, 2026.

  • #357 by @mcollina — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
73/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
api, backend

Research direction

The issue identifies the legacy SSE GET deadline calculation and its use of request.tokenPayload?.exp, but names no files or tests. Start by locating that handler and the built-in token path that reads exp, then inspect nearby tests for stream expiry and authorization responses. Done means the stream closes when the resolved expiresAt passes and an already expired context receives 401.

Written by the indexing model from the issue text.

Description

Summary

With resolveAuthorizationContext, the legacy SSE GET stream does not end when the resolved expiresAt passes. A context that has already expired is still served with 200.

Cause

The legacy GET works out its deadline from request.tokenPayload?.exp only. It never reads the resolved authorization context.

Repro

  • A resolver returns an expiresAt 300ms in the future. The legacy GET stream is still open after 1s.
  • A resolver returns an expiresAt that has already passed. The legacy GET still answers 200.

Suggested fix

Take the deadline from the resolved context's expiresAt, as the built-in token path does with exp. Answer an already-expired context with 401.

🤖 Generated with Claude Code

Dominant language
TypeScript
Stars
58
Forks
15
Avg merge
1d 7h
Merged PRs (30d)
53

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from platformatic/mcp

All issues in platformatic/mcp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.