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

Add a /health endpoint which does not require authentication

Open
#147 7 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
go
Domain
api

Research direction

Start with mux.go, where the request routes and authentication behavior can be traced. Add a GET /health endpoint that does not require authentication and returns HTTP 200 when the server is healthy; verify the endpoint is reachable without credentials and suitable for a Kubernetes livenessProbe.

Written by the indexing model from the issue text.

Description

Trying to deploy restic/rest-server:0.10.0 in k8s. I want a URL endpoint that I can use for "livenessProbe" (GET, should return 200).

As far as I can see from some testing, guided by mux.go - everything returns 401 Unauthorized. At the moment, I'm using a naive tcp 'liveness' probe, which is not nearly as expressive/accurate.

It would be nice if there was a /health endpoint (or similar) which did not require authentication, and returned 200 (assuming the server was ok).

Dominant language
Go
Stars
1.5k
Forks
179
Avg merge
15d 9h
Merged PRs (30d)
2

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a 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 restic/rest-server

All issues in restic/rest-server

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.