Use Squid for Its Exit IP Without Caching Pages

On a Squid release supporting the cache directive, use this rule to keep forwarding without response-cache reuse:

cache deny all

The directive prevents affected requests being satisfied from the response cache and prevents storing their responses. It does not delete existing cache files.

Keep access rules separate. http_access decides whether a client may make the request; cache decides response-cache use. Do not replace a denial with this rule or remove client, authentication and destination restrictions.

Outgoing address and routing rules still choose a direct source; a parent can still supply the final exit. DNS, logs, connection reuse and other internal state also remain. Disabling object reuse is not a way to choose a fresh IP.

A plain HTTPS CONNECT tunnel already hides the inner response from normal object caching. This rule does not change that TLS visibility. Use the directive documented for your release instead of assuming an old no_cache recipe has the same supported interface.