Confirmed users
9,511
edits
Firefox/Stub Attribution/Test Plan: Difference between revisions
Firefox/Stub Attribution/Test Plan (view source)
Revision as of 21:09, 3 January 2017
, 3 January 2017→Questions:
| Line 49: | Line 49: | ||
'''Notes on caching/timeout values:''' | '''Notes on caching/timeout values:''' | ||
# (Stub Attribition) HMAC_TIMEOUT is 10 minutes: https://github.com/mozilla-services/stubattribution/commit/8a6cc83547705d35451fb3ad08e3f82035f04abb | # (Stub Attribition) HMAC_TIMEOUT is 10 minutes: https://github.com/mozilla-services/stubattribution/commit/8a6cc83547705d35451fb3ad08e3f82035f04abb | ||
# (Bedrock) | # (Bedrock) stub-attribution cookie is now 24 hours: https://github.com/mozilla/bedrock/pull/4456/commits/4e8d5bb6bd6506d9cd2dfabef67ff2c780c8bbd9 | ||
#How can we test through cookied-Bedrock flow, at scale, for unique builds? | #How can we test through cookied-Bedrock flow, at scale, for unique builds? | ||
#How can we test (and try to break) Jeremy's 10-minute cache. And what does it cover, binary/condition-wise? (i.e. what's the driving logic/algorithm for caching vs. serving fresh?) | #How can we test (and try to break) Jeremy's 10-minute cache. And what does it cover, binary/condition-wise? (i.e. what's the driving logic/algorithm for caching vs. serving fresh?) | ||