Can't get bibxml3 for drafts with titles that end in a number

[ietf-svn-bot]

owner:housley@vigilsec.com resolution_fixed type_defect | by cabo@tzi.org

---

*** reference.I-D.brown-ec-2y2-x3-x-mod-8-to-91-plus-5.xml: *** Status code 404 while fetching https://datatracker.ietf.org/doc/bibxml3/draft-brown-ec-2y2-x3-x-mod-8-to-91-plus-5/xml
*** reference.I-D.ietf-oauth-v2-1.xml: *** Status code 404 while fetching https://datatracker.ietf.org/doc/bibxml3/draft-ietf-oauth-v2-1/xml
*** reference.I-D.olteanu-intarea-socks-6.xml: *** Status code 404 while fetching https://datatracker.ietf.org/doc/bibxml3/draft-olteanu-intarea-socks-6/xml

I don't understand the point of

    "rev": r"(?P<rev>[0-9]{1,2}(-[0-9]{2})?)",

for URL_REGEXPS in settings.py, which seems to directly cause the above failures.

---

Issue migrated from trac:3188 at 2022-03-04 08:10:34 +0000

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

Ugh - horrible (anti)-pattern at work again.

The root is the trouble in disambiguating the meaning of a string ending with -[0-9][0-9] (yes, that's {2} in both places in the regexp). Is that a title that ends with a number or the intent to signal a version?

The {1,2} above comes from a subtle mistake made with several other Document types, where we have documents whose version really is a single digit. The worst offender of this is documents of type 'slides'...

[ietf-svn-bot]

@rjsparks@nostrum.com changed priority from n/a to medium

[ietf-svn-bot]

@rjsparks@nostrum.com changed status from new to accepted

[ietf-svn-bot]

@housley@vigilsec.com changed status from accepted to assigned

[ietf-svn-bot]

@housley@vigilsec.com changed owner from `` to housley@vigilsec.com

[ietf-svn-bot]

@housley@vigilsec.com changed status from assigned to closed

[ietf-svn-bot]

@housley@vigilsec.com changed resolution from `` to fixed

[ietf-svn-bot]

@housley@vigilsec.com commented

---

Fixed in cb554fa:

Properly handle bibxml3 for drafts with filenames that end in a hypen and digits. Fixes #3188.

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

Fixed in c44c8a0:

Merged in cb554fa from housley@vigilsec.com:
Properly handle bibxml3 for drafts with filenames that end in a hypen and digits. Fixes #3188.

[ietf-svn-bot]

@cabo@tzi.org changed status from closed to reopened

[ietf-svn-bot]

@cabo@tzi.org changed resolution from fixed to ``

[ietf-svn-bot]

@cabo@tzi.org commented

---

That was a partial fix only:

https://datatracker.ietf.org/doc/bibxml3/draft-brown-ec-2y2-x3-x-mod-8-to-91-plus-5/xml -> reference.I-D.brown-ec-2y2-x3-x-mod-8-to-91-plus-5.xml (0.970 s)
*** reference.I-D.brown-ec-2y2-x3-x-mod-8-to-91-plus-5.xml: *** Status code 404 while fetching https://datatracker.ietf.org/doc/bibxml3/draft-brown-ec-2y2-x3-x-mod-8-to-91-plus-5-06/xml
https://datatracker.ietf.org/doc/bibxml3/draft-ietf-oauth-v2-1/xml -> reference.I-D.ietf-oauth-v2-1.xml (0.201 s)
*** reference.I-D.ietf-oauth-v2-1.xml: *** Status code 404 while fetching https://datatracker.ietf.org/doc/bibxml3/draft-ietf-oauth-v2-1-01/xml
https://datatracker.ietf.org/doc/bibxml3/draft-olteanu-intarea-socks-6/xml -> reference.I-D.olteanu-intarea-socks-6.xml (0.206 s)
*** reference.I-D.olteanu-intarea-socks-6.xml: *** Status code 404 while fetching https://datatracker.ietf.org/doc/bibxml3/draft-olteanu-intarea-socks-6-11/xml

[ietf-svn-bot]

@housley@vigilsec.com changed status from reopened to closed

[ietf-svn-bot]

@housley@vigilsec.com changed resolution from `` to fixed

[ietf-svn-bot]

@housley@vigilsec.com commented

---

Fixed in d42aab0:

Point bibxml3 to I-D archive so that all version numbers are handled properly, and perform more robust revision suffix cleanup. Fixes #3188.