---
title: "Overwrite host header in HTTP2 using the Chrome monitor"
slug: "overwrite-host-header-in-http2-using-the-chrome-monitor"
updated: 2023-01-06T15:49:07Z
published: 2023-01-06T15:49:07Z
canonical: "docs.catchpoint.com/overwrite-host-header-in-http2-using-the-chrome-monitor"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overwrite host header in HTTP2 using the Chrome monitor

When SPDY4/HTTP2 is enabled in Web/Transaction tests using the Chrome or Mobile monitor, overriding the host header field for HTTP2 requests served over HTTP should still work as expected, as HTTP2 requests served over HTTP are served over HTTP1.0.

HTTP2 recommends using pseudo-header fields **:authority** to represent **host** header information. However, please note that if the HTTP2 requests are served over HTTPS, overriding host header using **:authority** or **host** is not supported. When **:authority** or **host** is passed in the host header, the agent will ignore this host information and not pass the modified header information.

This is not applicable for Object or Playback tests, which do not support enabling SPDY4/HTTP2.

For more information on how to do a host override using our request override feature, please refer to our [request override guide](https://docs.catchpoint.com/docs/Request-Override-Guide). For an example on how host override is done, please read the "Option: Host Header" section of [this article](https://docs.catchpoint.com/docs/Difference-between-Host-in-the-URL-and-Host-Header)".