ACME challenge over HTTP/2 with HTTPS fails

Summary

ACME challenge over HTTP/2 with HTTPS fails

Steps to reproduce

Publish a file (example.com/.well-known/acme-challenge/file) and retrieve it over HTTP/2 with HTTPS (curl --http2 "https://example.com/.well-known/acme-challenge/file"). curl shows curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

Example Project

Link to example project (Link to job, Link to .gitlab-ci.yml)

What is the current bug behavior?

All files in /.well-known/acme-challenge/ retrieved with curl over HTTP/2 with HTTPS shows curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

What is the expected correct behavior?

File content should be retrieved without PROTOCOL_ERROR

Output of checks

This bug happens on GitLab.com