Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include section on cleartext req/resp headers #1377

Merged
merged 4 commits into from
Jan 23, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions FLEDGE_Key_Value_Server_API.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,12 @@ HTTPS is used to transport data. The method is `POST`.

The HTTP POST body is encrypted.

#### Cleartext headers
lusayaa marked this conversation as resolved.
Show resolved Hide resolved

Requests contain a cleartext HTTP `Content-Type` header with value `message/ad-auction-trusted-signals-request`.
lusayaa marked this conversation as resolved.
Show resolved Hide resolved

Responses contain a cleartext HTTP `Content-Type` header with value `message/ad-auction-trusted-signals-response`.
JensenPaul marked this conversation as resolved.
Show resolved Hide resolved

#### Encryption

We will use [Oblivious HTTP](https://datatracker.ietf.org/doc/draft-ietf-ohai-ohttp/) with the following configuration for encryption:
Expand Down
Loading