Http0.32.0

Each key describes the prefix of a request, and each value describes the replacement prefix.

This can be useful for setting up mirroring of packages, which are fetched over HTTPS.

In the case of multiple matches, the longest prefix is used.

The URL hostname is case-insensitive.

A replacement only happens once when resolving URLs. Therefore, the first replacement is the final URL that is used for the outbound request.

In the following example, an original request for https://pkg.pkl-lang.org/my/pkg@1.0.0 is replaced with https://my.internal.mirror/my/pkg@1.0.0.

This also affects 3XX status code redirect following.

Example:

rewrites {
  ["https://pkg.pkl-lang.org/"] = "https://my.internal.mirror/"
}

Rewrite targets must satisfy the following:

• It starts with either http://, or https://.
• It ends with /.
• It has a non-empty hostname.

An rewrite target should also not contain a query string or fragment component (not schematically enforced).

Each key is a glob pattern, and each value is a mapping of header name to header value(s).

Before an HTTP request is made, each key is matched against the request URL. If any matches are found, each of their described headers are added to the request.

To add headers to all HTTP requests, use ** as the glob pattern.

Example:

headers {
  // Add this user agent to all out-bound requests.
  ["**"] {
    ["User-Agent"] = "MyApp-Pkl"
  }

  // Add an authorization header to all requests made to the
  // `https://my.internal.service` host.
  ["https://my.internal.service/**"] {
    ["Authorization"] = "Bearer abc123"
  }
}

To repeat a header multiple times, set the value to a listing:

headers {
  // Adds:
  //   My-Custom-Header: foo
  //   My-Custom-Header: bar
  ["**"] {
    ["My-Custom-Header"] { "foo"; "bar" }
  }
}

For details on glob patterns, see https://pkl-lang.org/main/current/language-reference/index.html#glob-patterns.