# io.k8s.api.networking.v1.HTTPIngressPath

From **Kubernetes**.

HTTPIngressPath associates a path with a backend. Incoming urls matching the path are forwarded to the backend.

- Type: `object`

## Properties

### `backend`

- Required: true
- Default: `{}`

backend defines the referenced service endpoint to which the traffic will be forwarded to.

### `path`

- Required: false
- Type: `string`

path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional "path" part of a URL as defined by RFC 3986. Paths must begin with a '/' and must be present when using PathType with value "Exact" or "Prefix".

### `pathType`

- Required: true
- Type: `string`

pathType determines the interpretation of the path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is
  done on a path element by element basis. A path element refers is the
  list of labels in the path split by the '/' separator. A request is a
  match for path p if every p is an element-wise prefix of p of the
  request path. Note that if the last element of the path is a substring
  of the last element in request path, it is not a match (e.g. /foo/bar
  matches /foo/bar/baz, but does not match /foo/barbaz).
* ImplementationSpecific: Interpretation of the Path matching is up to
  the IngressClass. Implementations can treat this as a separate PathType
  or treat it identically to Prefix or Exact path types.
Implementations are required to support all path types.

## JSON Schema

```json
{"description":"HTTPIngressPath associates a path with a backend. Incoming urls matching the path are forwarded to the backend.","properties":{"backend":{"allOf":[{"$ref":"#/components/schemas/io.k8s.api.networking.v1.IngressBackend"}],"default":{},"description":"backend defines the referenced service endpoint to which the traffic will be forwarded to."},"path":{"description":"path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional \"path\" part of a URL as defined by RFC 3986. Paths must begin with a '/' and must be present when using PathType with value \"Exact\" or \"Prefix\".","type":"string"},"pathType":{"description":"pathType determines the interpretation of the path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is\n  done on a path element by element basis. A path element refers is the\n  list of labels in the path split by the '/' separator. A request is a\n  match for path p if every p is an element-wise prefix of p of the\n  request path. Note that if the last element of the path is a substring\n  of the last element in request path, it is not a match (e.g. /foo/bar\n  matches /foo/bar/baz, but does not match /foo/barbaz).\n* ImplementationSpecific: Interpretation of the Path matching is up to\n  the IngressClass. Implementations can treat this as a separate PathType\n  or treat it identically to Prefix or Exact path types.\nImplementations are required to support all path types.","type":"string"}},"required":["pathType","backend"],"type":"object"}
```