> For the complete documentation index, see [llms.txt](https://fabco.gitbook.io/dappy-spec/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fabco.gitbook.io/dappy-spec/sections-specific-to-browser-and-web-applications/transport-layer-security-http+tls.md).

# TLS / encrypted traffic only and HSTS

TLS (Transport Layer Security) (sometimes refered to as SSL) has been around for almost 20 years. It is mandatory in dappy, unencrypted HTTP traffic does not exist. For browser to node (network member) it only accepts TLSv1.3, and for regular browser to servers communication it only accepts TLSv1.2+ .

This of course makes a lot of MITM attacks impossible to perform.

[See it in the dappy codebase](https://github.com/fabcotech/dappy/blob/master/main/overrideHttpProtocols.ts#L229)

### HSTS (HTTP Strict Transport Security)

HSTS (HTTP Strict Transport Security)  is a feature communicated by web servers to browsers through HTTP headers, that tells the browser to exclusively rely on HTTPS for all the in/out connections in a given session. It is of course useless in dappy since it is already a exclusively HTTP+TLS web browser.

[Mozilla's documentaion](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security) on HSTS


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fabco.gitbook.io/dappy-spec/sections-specific-to-browser-and-web-applications/transport-layer-security-http+tls.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.