2 min • read

Host headers

Emissary-ingress supports several different methods for managing the HTTP Host header.

Using host and host_regex

A mapping that specifies the host attribute will take effect only if the HTTP Host header matches the value in the host attribute. If host_regex is true, the host value is taken to be a regular expression. Otherwise, an exact string match is required.

You may have multiple mappings listing the same resource but different host attributes to effect Host-based routing. An example:

will map requests for / to

  • the quote2 service if the Host header is quote.datawire.io;
  • the quote3 service if the Host header matches ^quote[2-9]\\.datawire\\.io$; and to
  • the quote1 service otherwise.

Note that enclosing regular expressions in quotes can be important to prevent backslashes from being doubled.

Using host_rewrite

By default, the Host header is not altered when talking to the service -- whatever Host header the client gave to Emissary-ingress will be presented to the service. For many microservices, this will be fine, but if you use Emissary-ingress to route to services that use the Host header for routing, it's likely to fail (legacy monoliths are particularly susceptible to this, as well as external services). You can use host_rewrite to force the Host header to whatever value that such target services need.

An example: the default Emissary-ingress configuration includes the following mapping for httpbin.org:

As it happens, httpbin.org is virtually hosted, and it simply will not function without a Host header of httpbin.org, which means that the host_rewrite attribute is necessary here.

host and method


  • the host attribute becomes a header match on the :authority header; and
  • the method attribute becomes a header match on the :method header.

You will see these headers in the diagnostic service if you use the method or host attributes.