Practise the standard verbs for managing CORS preflight caching.
0 / 5 completed
1 / 5
Fill in: 'We ___ preflight responses so the browser doesn't re-send an OPTIONS request on every single call.'
We 'cache a response' — the standard collocation for storing a result to avoid repeating the request. The other options aren't idiomatic here.
2 / 5
Fill in: 'A missing Access-Control-Max-Age header can ___ the browser into repeating a preflight for every request.'
We say a missing header will 'force' repeated preflights — the standard collocation for the resulting behaviour. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ allowed origins explicitly instead of reflecting whatever Origin header a request happens to send.'
We 'declare' origins — the standard collocation for explicitly listing permitted values. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ CORS headers in dev tools whenever a cross-origin call fails mysteriously in the browser.'
We 'inspect' headers — the standard, established debugging collocation for examining response metadata. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ the preflight cache lifetime conservatively so a revoked origin doesn't stay trusted too long.'
We 'limit' a lifetime — the standard collocation for bounding how long a cached value stays valid. The other options aren't idiomatic here.