# HTTP/2, Chrome 49 on Windows XP problems

**URL:** <https://discourse.haproxy.org/t/http-2-chrome-49-on-windows-xp-problems/2931>\
**Category:** Help!\
**Created:** [August 31, 2018, 2:00pm UTC](https://discourse.haproxy.org/t/http-2-chrome-49-on-windows-xp-problems/2931 "2018-08-31T14:00:14Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [August 31, 2018, 2:20pm UTC](https://discourse.haproxy.org/t/http-2-chrome-49-on-windows-xp-problems/2931/2 "2018-08-31T14:20:01Z")

</div>

I assume you don’t want to hear that Chrome 49 is completely outdated.

This specific issue is caused by a bug in the blink engine of Chrome 49, which is causing H2 to fail when using long URLs, you can read more about it here:

> [@HTTP/2 not compatible with filrefox on haproxy 1.8.3?](https://discourse.haproxy.org/t/http-2-not-compatible-with-filrefox-on-haproxy-1-8-3/2075/32):
>
> I’ve found the root of the rest problem: The max length of url has very strict limitation under the h2 mode on some old versions of the chrome blink engine. Even if the same url just working fine under the http/1.1 mode with the exactly same blink engine. For example: We have an url with 2713 bytes of length, and it is not working under h2 mode for the chrome 49. The solution is very simple: Just shrink the url length. For example, we have a function deal with the js file batch loading, here i…

---

_[View the full topic](https://discourse.haproxy.org/t/http-2-chrome-49-on-windows-xp-problems/2931)._