Repository navigation
|
Hi, I’m trying to use a custom According to the settings docs, https://mise.jdx.dev/configuration/settings.html#netrc However, it looks like this only applies to mise’s main HTTP client, not to HTTP requests made from the vfox runtime. From a quick code read:
So requests made by:
do not appear to use Is this expected behavior? If yes, should the documentation clarify that If no, would it make sense to expose netrc support to the vfox runtime, so custom backend plugins can access private artifact repositories without manually passing Thanks. |
Replies: 1 comment
|
Thanks for the detailed investigation — your read is correct. Now that vfox supports URL replacements, netrc authentication should apply consistently to its HTTP requests as well. I opened #12168. It keeps netrc settings and parsing in mise, then supplies destination-specific headers to vfox after URL rewriting. This covers traditional The PR includes unit coverage for rewritten direct and Lua requests, plus an end-to-end test where the mirror rejects every request without the expected Basic auth header. AI-assisted — Tool: Codex; model: OpenAI/GPT-5; version: unavailable. |
Thanks for the detailed investigation — your read is correct. Now that vfox supports URL replacements, netrc authentication should apply consistently to its HTTP requests as well.
I opened #12168. It keeps netrc settings and parsing in mise, then supplies destination-specific headers to vfox after URL rewriting. This covers traditional
pre_install.urldownloads plus the Lua HTTP helpers used fromBackendListVersions,BackendInstall, and other hooks. Explicit plugin authorization still takes precedence for same-origin requests.The PR includes unit coverage for rewritten direct and Lua requests, plus an end-to-end test where the mirror rejects every request without the expected Basic auth …