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

Add support for Ad-Auction-Result-Nonce header #1393

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

brusshamilton
Copy link
Contributor

@brusshamilton brusshamilton commented Feb 4, 2025

No description provided.

@brusshamilton
Copy link
Contributor Author

@qingxinwu PTAL

@qingxinwu qingxinwu added the spec Relates to the spec label Feb 4, 2025
spec.bs Outdated Show resolved Hide resolved
spec.bs Outdated Show resolved Hide resolved
spec.bs Show resolved Hide resolved
spec.bs Outdated Show resolved Hide resolved
spec.bs Outdated
[=traversable navigable's=] [=traversable navigable/captured ad auction result nonce headers=].
1. Let |seller| be |auctionConfig|'s [=auction config/seller=].
1. If |capturedAuctionNonceHeaders|[|seller|] does not [=map/exist=] or does not
[=list/contain=] the [=string representation=] of |response|'s
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are both of these guaranteed to be lowercase somewhere? In code, I saw we lowercased the nonces. We need to do it in the spec as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. I had previously assumed that UUIDs were canonically lowercase. It turns out that the case is canonically arbitrary 🤷.

@@ -3193,6 +3188,20 @@ a [=list=] of [=interest groups=] |bidIgs|, and a [=reporting context map=]
1. Let |response| be the [=server auction response=] which is the result of
deserializing |auctionConfig|'s [=auction config/server response=]
with |requestContext| according to [Section 2.3.5 of the Bidding and Auction Services IETF standard](https://privacysandbox.github.io/draft-ietf-bidding-and-auction-services/draft-ietf-bidding-and-auction-services.html#name-parsing-a-response).
1. If |response|'s [=server auction response/nonce=] [=map/exists=]:
1. Let |capturedAuctionNonceHeaders| be |global|'s [=associated Document's=] [=node navigable's=]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is nonce always lowercase in the result nonce header?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec Relates to the spec
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants