# https

> The https identity: HTTP over TLS. Every directive and what is required.

`https` is HTTP over TLS (RFC 2818). It uses the [http](/docs/solution/identity/http/) directives: a method directive (`get`/`post`) plus `with the header`, `with the cookie`, `capture`, and `expect`. The target is a base URL with an `https://` scheme. The `http` identity also covers both schemes, so a plain `http` solution works against an `https` target; `https` exists so a solution can name the secure scheme explicitly.

## Example

```text
https reflect
  get with "REFLECTED_7x7"
  # send a unique marker and confirm it comes back over TLS
  expect "REFLECTED_7x7" in the response
```