ExternalName enhancements
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
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:
- the method limitation (only HEAD/GET/OPTIONS) stems from the
reqwestimplementation, it can go away by using https://docs.rs/varnish/latest/varnish/vcl/struct.Ctx.html#method.req_body) - the
reqwestcode was inspired by https://github.com/varnish-rs/vmod-reqwest, which doesn't use an async runtime anymore forbackendfetches anymore, so we can align the code and simplify the logic a bit - the
hostheader being forced is problematic as we may need to override it. I'm not sure how to handle this right now, but I'll look at it
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from varnish/gateway
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 5 days
-
beta documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
varnish/gateway#58 · 1 comment ·
Maintainers usually reply within 5 days
-
beta documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
varnish/gateway#52 · 1 comment ·
Maintainers usually reply within 5 days
-
beta enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 5 days
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
varnish/gateway#123 · 1 comment ·
Maintainers usually reply within 5 days
Similar issues
-
Date tests fail when the local date differs from the UTC datePossibly taken @unidoc-alip claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
rossoctl/context-guru#1217 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
router-for-me/CLIProxyAPI#7659 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netsampler/goflow2#601 ·
Maintainers usually reply within 1 day