Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kramdown-rfc fails to recognize web proxy #253

Open
mouse07410 opened this issue Mar 16, 2025 · 2 comments
Open

kramdown-rfc fails to recognize web proxy #253

mouse07410 opened this issue Mar 16, 2025 · 2 comments

Comments

@mouse07410
Copy link

See martinthomson/i-d-template#472

Toolchain pulls reference.RFC.*.xml files from Internet. On my system it requires using Web proxy , defined in env vars HTTP_PROXY, HTTPS_PROXY and such.

Somehow, those settings are ignored:

.  .  .
/Users/ur20980/.cache/xml2rfc/reference.RFC.4306.xml: renewing (stale by 10.6 days) from https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4306.xml
/Users/ur20980/.cache/xml2rfc/reference.RFC.2459.xml: renewing (stale by 10.6 days) from https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2459.xml
/Users/ur20980/.cache/xml2rfc/reference.RFC.2119.xml: renewing (stale by 10.6 days) from https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml
/Users/ur20980/.cache/xml2rfc/reference.RFC.8174.xml: renewing (stale by 10.6 days) from https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml
/Users/ur20980/.cache/xml2rfc/reference.RFC.5247.xml: renewing (stale by 10.6 days) from https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5247.xml
make: *** [draft-uri-lamps-pquake.xml] Error 127
make: *** Deleting file `draft-uri-lamps-pquake.xml'

Of course, one workaround that I use is manually downloading those RFCs and placing them in the expected dir. But it would be much less irritating if the toolchain could manage this task by itself.

@cabo
Copy link
Owner

cabo commented Mar 16, 2025

Hi,

I'm not seeing in the above any error messages related to the fetches; the messages look like a normal trace of fetching the I-Ds.
I would expect messages like "*** Can't get with persistent HTTP: Failed to open TCP connection" if you can't use HTTP directly.
(It doesn't help that I don't know whether you are using KRAMDOWN_PERSISTENT -- I-D-template normally does.)
Anyway, all looks normal so far, and I don't know where the error 127 then comes in.

In any case, I have found a way to explicitly feed the environment variables to net/http/persistent, and I will release a new revision presently.

@cabo
Copy link
Owner

cabo commented Mar 16, 2025

In any case, I have found a way to explicitly feed the environment variables to net/http/persistent, and I will release a new revision presently.

Now in 1.7.26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants