We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It looks like some RFCs use different markup from others, leading to the RFC fetcher to fail to extract the title.
For example, https://datatracker.ietf.org/doc/html/rfc3986 uses
<span class="h1">Uniform Resource Identifier (URI): Generic Syntax</span>
and is successfully matched by
title = xml.xpath('string(//span[@class="h1"])')
but e.g., https://datatracker.ietf.org/doc/html/rfc9110 uses
<h1 id="title">HTTP Semantics</h1>
and is not matched.
It's possible that adding
if not title: title = xml.xpath('string(//h1[@id="title"])')
in https://github.com/sipb/chiron/blob/master/chiron_bot/fetchers.py fetch_rfc might help, but I didn't test this.
fetch_rfc
The text was updated successfully, but these errors were encountered:
If you use https://www.rfc-editor.org/info/rfcXXX as the URL, that has consistent formatting for all RFC metadata.
https://www.rfc-editor.org/info/rfcXXX
Sorry, something went wrong.
(And the IETF considers rfc-editor.org the canonical site for published RFCs)
Ah, yes, I thought we had talked about that before. :-)
#42
No branches or pull requests
It looks like some RFCs use different markup from others, leading to the RFC fetcher to fail to extract the title.
For example, https://datatracker.ietf.org/doc/html/rfc3986 uses
and is successfully matched by
but e.g., https://datatracker.ietf.org/doc/html/rfc9110 uses
and is not matched.
It's possible that adding
in https://github.com/sipb/chiron/blob/master/chiron_bot/fetchers.py
fetch_rfc
might help, but I didn't test this.The text was updated successfully, but these errors were encountered: