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

Add debug logging around requests

Open
#7,396 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript

Research direction

The issue does not name any files, tests, or entry points. First map how requests, authentication, cookies, rate limiting, and configuration are handled, then define safe logging requirements and verify that request and response details do not expose sensitive data.

Written by the indexing model from the issue text.

Description

enhancement

We should log the start and stop of all requests. Probably a request ID, endpoint, method, and payload for the start log, and then a request ID, status code, response body, and duration for the end log.

And some auth, cookie info, and rate limit info to debug login issues. It would be convenient to see something like "returning a 401 because the cookie did not match the value stored in password" or "request has been rate limited" or whatever the case may be.

Additionally, a configuration knob for the rate limit would be useful for debugging (perhaps just a disable toggle).

Dominant language
TypeScript
Stars
79.4k
Forks
6.9k
Avg merge
2d 13h
Merged PRs (30d)
39

Contributor guide

Open the 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 coder/code-server

All issues in coder/code-server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.