Practise the standard verbs for configuring an nginx reverse proxy correctly.
0 / 5 completed
1 / 5
Fill in: 'We ___ a reverse proxy in front of the app servers, rather than exposing every backend directly to the actual public internet.'
We 'configure a proxy' — the standard, simple collocation for setting up nginx as a reverse proxy. The other options are less idiomatic here.
2 / 5
Fill in: 'A missing X-Forwarded-For header on the proxy can ___ the backend logging the proxy's IP instead of the actual client's.'
We say a missing header will 'leave' the backend logging the wrong IP — the standard, natural collocation for the resulting inaccuracy. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ upstream timeouts explicitly per location block, rather than a default that kills a slow but actually legitimate request.'
We 'set timeouts' — the standard, simple collocation for configuring nginx upstream timeout values. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every proxy config change with nginx -t before reload, rather than pushing syntax nobody's actually validated.'
We 'validate a config' — the standard, simple collocation for testing nginx configuration syntax before applying it. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ upstream response times through the access log continuously, rather than assuming the proxy is actually adding no latency.'
We 'monitor response times' — the standard, simple collocation for watching proxy performance over time. The other options aren't idiomatic here.