# HTTP\_PROXY/HTTPS\_PROXY issues

**URL:** <https://forum.ecmwf.int/t/http-proxy-https-proxy-issues/906>\
**Category:** API\
**Tags:** api, c3s\
**Created:** [18 February 2020 09:33 UTC](https://forum.ecmwf.int/t/http-proxy-https-proxy-issues/906 "2020-02-18T09:33:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michela](https://forum.ecmwf.int/letter_avatar_proxy/v4/letter/m/898d66/32.png) [@Michela](https://forum.ecmwf.int/u/Michela)\
**Post date:** [18 February 2020 09:33 UTC](https://forum.ecmwf.int/t/http-proxy-https-proxy-issues/906/1 "2020-02-18T09:33:18Z")

</div>

CDS API requests could sometimes fail because it does not pick up the right proxy when&nbsp;the client script comes to download the data.

An option is to manually set HTTP\_PROXY/HTTPS\_PROXY&nbsp; **explicitly** with the port number used and then re-running the script.

Here an example:

The users system were only set to:

```
export HTTP_PROXY=http://useraddress

export HTTPS\_PROXY=[http://useraddress](http://useraddress)
```

This was resolved by explicitly specifing the port on the proxy to use at the user's site for port 80/8080 connections:

```
export HTTP_PROXY=http://useraddress:userport/

export HTTPS\_PROXY=[http://useraddress](http://useraddress):userport/
```

Note that you are also able to download the datafile using wget.