Now that bibxml3 xml2rfc path resolution uses Datatracker to check the latest version of a draft, when we use xml2rfc path resolution checker tool to see how bibxml3 paths resolve BibXML service bombards Datatracker with requests (one for every file shown to the user).
I’m considering allowing xml2rfc resolvers to see the requested-with headers, and the internet draft resolver could skip checking Datatracker response if the header is appropriately set by the internal tool.
Now that bibxml3 xml2rfc path resolution uses Datatracker to check the latest version of a draft, when we use xml2rfc path resolution checker tool to see how bibxml3 paths resolve BibXML service bombards Datatracker with requests (one for every file shown to the user).
I’m considering allowing xml2rfc resolvers to see the requested-with headers, and the internet draft resolver could skip checking Datatracker response if the header is appropriately set by the internal tool.