cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted

HTTP/2

In the release notes of version 7.6.2.11 you will find in Resolved issues:

When filtering HTTP2 traffic was enabled on Web Gateway, processing failed for gmail POST requests that had been sent using the Chrome and Firefox browsers. (1188899)

We use version 7.6.2.12 but we can't find a way to turn Http/2 on or off.

Any Hints?

6 Replies
Highlighted
Level 9
Report Inappropriate Content
Message 2 of 7

Re: HTTP/2

I am not sure about 7.6.x, don't have that running at the moment. But in 7.7.2 you can use the Enable proxy control event to override use (and max. header length) of HTTP/2. Since you're able to use any criteria in a rule where you use that event, you can do it just for problematic sites, combination of site/user-agent or globally.

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 3 of 7

Re: HTTP/2

Hi together,

maybe it is not wrong to consider upgrading to latest version 7.7.2.6 since there are several HTTP2 bugs/issues already fixed in 7.7.2.x.

Here you will find a summary of the release notes:

Since I am not sure if this article is always kept up to date, you can also have a look here:

https://contentsecurity.mcafee.com

Regards,

Marcel

Regards,
Marcel Kutrieba
Technical Support Engineer
Highlighted

Re: HTTP/2

I know how to configure HTTP/2 under 7.7. Unfortunately, we will have to work under 7.6 for at least another 6 months.

So the question how can I enable HTTP/2 under 7.6? In the Release Notes, several bug fixes are used to indicate the presence of the option.

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 5 of 7

Re: HTTP/2

Hello Frank,

This is just wrong information in the release notes. There is no support of HTTP2 in 7.6.

I also checked the bug ID and there is only information for 7.7.1 and 7.7.2. I will check this with the documentation team and get this PDF updated.

Regards,

Stefan

Highlighted
Level 10
Report Inappropriate Content
Message 6 of 7

Re: HTTP/2

I submitted this as a documentation bug a while ago I believe. (I think I sent it to Jon directly to pass on actually). Looked like it just got tagged on by mistake with the related 7.7.x release at the time.

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 7 of 7

Re: HTTP/2

Hello pcoates,

I have forwarded this change directly to the documentation team. McAfee normally does not edit release notes of existing versions, but will handle this change this time.

Kind regards,

Stefan

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community