evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "Evaluates how well the solution configures make-fetch-happen for proxy routing, TLS trust, DNS caching, and socket pooling as outlined in the spec. Focus stays solely on correct usage of make-fetch-happen options tied to those behaviors.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Proxy routing",
"description": "Uses makeFetchHappen with both http/https proxy URLs and a noProxy list via opts.proxy/opts.noProxy so bypassed hosts connect directly while other hosts go through the correct proxy.",
"max_score": 30
},
{
"name": "TLS credentials",
"description": "Passes strictSSL together with ca/cert/key options into makeFetchHappen so strict mode enforces the provided CA chain while strictSSL false permits self-signed endpoints.",
"max_score": 25
},
{
"name": "DNS cache TTL",
"description": "Configures opts.dns (such as ttl or a lookup wrapper) on makeFetchHappen to cache hostname resolutions for the specified TTL and trigger fresh lookups after expiry.",
"max_score": 20
},
{
"name": "Socket pooling",
"description": "Sets agent pooling on makeFetchHappen (via opts.agent or opts.maxSockets) so keep-alive sockets are reused up to the configured per-origin limit.",
"max_score": 25
}
]
}