| additional-bids.py |
Endpoint to return additional bids in the appropriate response header.
Additional bids are returned using the "Ad-Auction-Additional-Bid" response
header, as described at
https://github.com/WICG/turtledove/blob/main/FLEDGE.md#63-http-response-headers.
This script generates one of "Ad-Auction-Additional-Bid" response header for
each additional bid provided in a url-encoded `additionalBids` query parameter.
All requests to this endpoint requires a "Sec-Ad-Auction-Fetch" request header
with a value of b"?1"; this entrypoint otherwise returns a 400 response.
|
5557 |
| authorize-server-response.py |
|
253 |
| ba-fledge-util.sub.js |
|
11461 |
| ba-public-keys |
|
110 |
| bidding-logic.sub.py |
function generateBid(interestGroup, auctionSignals, perBuyerSignals,
trustedBiddingSignals, browserSignals,
directFromSellerSignals,
crossOriginTrustedBiddingSignals) {{
{{{{GET[generateBid]}}}};
return {{
bid: {bid},
{bidCurrency}
{allowComponentAuction}
render: interestGroup.ads[0].renderURL
}};
}} |
3364 |
| decision-logic.sub.py |
function scoreAd(adMetadata, bid, auctionConfig, trustedScoringSignals,
browserSignals, directFromSellerSignals,
crossOriginTrustedScoringSignals) {
// Don't bid on interest group with the wrong uuid. This is to prevent
// left over interest groups from other tests from affecting auction
// results.
if (!browserSignals.renderURL.endsWith('uuid={{GET[uuid]}}') &&
!browserSignals.renderURL.includes('uuid={{GET[uuid]}}&')) {
return 0;
}
{{GET[scoreAd]}};
return {desirability: 2 * bid, allowComponentAuction: true};
} |
2823 |
| direct-from-seller-signals.py |
|
5533 |
| ed25519.py |
NB: This code is not safe for use with secret keys or secret data.
The only safe use of this code is for verifying signatures on public messages.
Functions for computing the public key of a secret key and for signing
a message are included, namely publickey_unsafe and signature_unsafe,
for testing purposes only.
The root of the problem is that Python's long-integer arithmetic is
not designed for use in cryptography. Specifically, it may take more
or less time to execute an operation depending on the values of the
inputs, and its memory access patterns may also depend on the inputs.
This opens it to timing and cache side-channel attacks which can
disclose data to an attacker. We rely on Python's long-integer
arithmetic, so we cannot handle secrets without risking their disclosure.
|
7228 |
| empty.html |
|
16 |
| fenced-frame.sub.py |
<!DOCTYPE html>
<html>
<head>
<!--- Allow injected scripts to use functions in fledge-util.sub.js --->
<base href="..">
<script src="/resources/testharness.js"></script>
<script src="/common/utils.js"></script>
<script src="resources/fledge-util.sub.js"></script>
</head>
<body>
<script>
{{GET[script]}}
</script>
</body>
</html>
|
819 |
| fledge-util.sub.js |
|
41015 |
| fledge_http_server_util.py |
Utility functions shared across multiple endpoints. |
5511 |
| incrementer.wasm |
|
46 |
| permissions.py |
Methods for the interest group cross-origin permissions endpoint. |
2259 |
| real-time-report.py |
Handles POST request for reports.
Retrieves the report from the request body and stores the report in the
stash. If clear_stash is specified in the query params, clears the stash.
|
2713 |
| redirect-to-trusted-signals.py |
|
1136 |
| redirect.py |
|
518 |
| request-tracker.py |
|
6469 |
| service-worker-helper.js |
|
774 |
|
|
42 |
| set-cookie.asis |
|
51 |
| subordinate-frame.sub.html |
|
3933 |
|
|
38 |
| trusted-bidding-signals.py |
|
6759 |
| trusted-scoring-signals.py |
|
4834 |
| update-url.py |
|
243 |
| wasm-helper.py |
|
1352 |
| worklet-helpers.js |
|
693 |