Problem with HTTP2 profiles on 13.1.0.1?

There are some bugs related to HTTP2 in the release notes:

https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/related/relnote-supplement-bigip-13-1-0-1.html

See the section "Known Issues in BIG-IP v13.1.x". There are explanation and workaround at the end, and some may have already been fixed for 13.1.0.1.

I have the same issue. In 13.1 there is no longer the NPN mode in the advanced settings for the http2 profile only ALPN and Always. I was about to open a ticket but as a workaround I have removed the http2 profile from my virtual servers.

Hi Dan,

Any news on this issue? Did you get any answer from the support ?

We are facing exactly the same problem, and have fixed it for now by disabling HTTP/2.

The same issue is affecting us on 13.1.0.2 (we've opened a support call C2634426, awaiting a response). Logging the request headers on the F5 seems to show the Accept header with an empty header name, though a packet capture of the request from Firefox looks sane, so it looks like there are some issues with header processing.

We've had a response to our support call to say this is a bug:

ID703191 HTTP2 requests may contain invalid headers when sent to servers

Good news Mat,

Do you have any idea when it will be patched ?

I've been having the same header issue with Firefox, turning on http2 changes "accept: text/css,/;q=0.1\r\" to ": text/css,/;q=0.1\r\n"

We received an Engineering hot fix for 13.1.0.2, but I don't know when this will be included in an official release.

13.1.0.3 has been released yesterday. In the list of known issues in the release notes:

703191-2 2-Critical HTTP2 requests may contain invalid headers when sent to servers

Details of the issue in the release notes:

703191-2 : HTTP2 requests may contain invalid headers when sent to servers

Component: Local Traffic Manager

Symptoms:
HTTP requests handled by an HTTP/2 virtual server may have blank header names when proxied through to the server or when handled via iRules.

Conditions:
-- Virtual server has the HTTP/2 profile assigned.
-- Client and the BIG-IP system negotiate/use HTTP/2.

Impact:
HTTP/2 applications may generate CSRF-related errors. Alternately, the server may return intermittent (and from the client's perspective, spurious) 400 Bad Request responses.

Workaround:
There is no workaround other than to remove the HTTP/2 profile from the virtual server.

Hello We run 13.1.0.4 and are still facing the HTTP Error 400 "The request has an invalid header name" when using the http2 profile. The 13.1.0.4 release note still mentions bug 703191-2 in the list of known bugs (and so does 13.1.0.5 release note). Is F5 working on this issue ?