<commit_before>---
title: Enable HTTP/2
menu:
  product_voyager_9.0.0:
    identifier: enable-http-2
    name: Enable HTTP/2
    parent: Enable HTTP/2
    weight: 10
product_name: voyager
menu_name: product_voyager_9.0.0
section_menu_id: guides
---
> New to Voyager? Please start [here](/docs/concepts/overview.md).

# Enable HTTP/2

You can configure HTTP/2 by configuring `proto` or, `alpn` under `rules.http` section (for frontend) or, `backend` section (for specific backend). If you want to use only `HTTP/2.0`, then you can specify it using `proto: h2`. However, if you like to use both `HTTP/2.0` and `HTTP/1.1` in a preferred order, then you need to specify the order using `ALPN`.

Please note the followings:
- TLS needed to be configured for using `ALPN`.
- A single rule/backend can't use both `ALPN` and `proto`.
- Multiple rules pointing the same frontend can't use different `ALPN` or, `proto` configurations.

## Example: gRPC Without TLS

First create demo namespace for this example.
<commit_msg>Fix hugo frontmatter for HTTP/2 doc (#1353)<commit_after>---
title: Configure HTTP/2 and GRPC | Kubernetes Ingress
menu:
  product_voyager_9.0.0:
    identifier: enable-http-2
    name: Configure HTTP/2 and GRPC
    parent: config-ingress
    weight: 10
product_name: voyager
menu_name: product_voyager_9.0.0
section_menu_id: guides
---

> New to Voyager? Please start [here](/docs/concepts/overview.md).

# Configure HTTP/2 and GRPC

You can configure HTTP/2 by configuring `proto` or, `alpn` under `rules.http` section (for frontend) or, `backend` section (for specific backend). If you want to use only `HTTP/2.0`, then you can specify it using `proto: h2`. However, if you like to use both `HTTP/2.0` and `HTTP/1.1` in a preferred order, then you need to specify the order using `ALPN`.

Please note the followings:
- TLS needed to be configured for using `ALPN`.
- A single rule/backend can't use both `ALPN` and `proto`.
- Multiple rules pointing the same frontend can't use different `ALPN` or, `proto` configurations.

## Example: gRPC Without TLS

First create demo namespace for this example.

{'fraction_non_alphanumeric': 0.10155880963627775, 'fraction_numerical': 0.02172886159659896, 'mean_word_length': 4.00709219858156, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5515679', 'n_tokens_mistral': 690, 'n_tokens_neox': 663, 'n_words': 279}