HTTP lexer fails on HTTP/2.0 (HTTP/2 works)

[rugk]

HTTP/2 defines pseudo-headers with colons:
https://stackoverflow.com/a/38471412/5008962

E.g.

POST /access/sdk/anonymous HTTP/2.0
:authority: example.zendesk.com

{}

in https://pygments.org/demo/#try

results in a bad image

Also reproduced locally with:

$ pygmentize -V       
Pygments version 2.4.2, (c) 2006-2019 by Georg Brandl.

[rugk]

Ohhh no, I now just see it's not (only) the header where it fails, it misses HTTP/2 support altogether, because this works:

POST /access/sdk/anonymous HTTP/1.1
:authority: example.zendesk.com

{}

It only highlights the colon:

POST /access/sdk/anonymous HTTP/1.1
:authority: example.zendesk.com

{}

But this totally fails:

POST /access/sdk/anonymous HTTP/2.0
:authority: example.zendesk.com

{}

[rugk]

Oh sorry, just see support has been added in v2.6.1 for this, Sry.

[rugk]

Though this does not explain why it does not work on https://pygments.org/demo/#try

Also could there be a bug?
If I patched my local version with the this new lexer it did not work, becaaaause…

ah… only HTTP/2 works, but my examples are real-life ones, so I guess you interpret the spec wrong.

[rugk]

Okay, opened a PR now: #1521

[rugk]

Aaand, as I just notice, the colon issue is still present. Thus opening this as a new issue: #1523