ExternalName enhancements

Open
#87 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
go, rust
Domain
backend

Research direction

The issue is a maintainer TODO list covering three separate changes to the ExternalName backend: dropping the reqwest-based fetch in favour of the Varnish Rust Ctx request body API, aligning with vmod-reqwest's non-async backend fetch, and deciding how to handle the forced Host header. No file paths are named, so first locate the reqwest-based ExternalName code and the Host header override. Done means a decision on the Host header and a plan or PR for each item, which needs maintainer input first.

Written by the indexing model from the issue text.

Description

Creating this as a TODO list as all the changes are in the same area and can/should most likely be handled as a batch:

Dominant language
Go
Stars
16
Forks
3
Avg merge
5d 15h
Merged PRs (30d)
10

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 varnish/gateway

All issues in varnish/gateway

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.