Launch contextily's Tile Downloader with the Proxy Environment

Apply Requests proxy and trust inputs to the Python worker, then distinguish a real tile download from cache reuse.

export HTTP_PROXY=http://proxy.example:8080
export HTTPS_PROXY=http://proxy.example:8080
python map_job.py

contextily's standard web-tile path uses Requests. Give the variables to the process running map_job.py; a notebook kernel or scheduled worker needs its own launch environment. Both destination schemes can use the same HTTP intermediary. For public tiles on a permitted public-proxy route, choose an endpoint from the HTTP proxy list for these values.

Conda's package-manager proxy settings do not automatically configure these later Python requests.

If HTTPS fails on an organization's CA, configure Requests trust in that worker, for example with its approved REQUESTS_CA_BUNDLE. Ordinary proxy selection does not require replacing contextily's private downloader or removing HTTP error checks.

When a basemap renders with no matching proxy request, establish whether it reused cached tiles. Inspect an operation that genuinely needs a download before concluding the environment was ignored.

The tile-provider URL remains the content destination, with its existing authentication, attribution and permitted-download policy.

Allakkat attuumassuteqartut