Access to Wallarm API via Proxy¶
These instructions describe the steps to configure access to Wallarm API via the proxy server.
-
https://api.wallarm.com:444/for the EU Cloud -
https://us1.api.wallarm.com:444/for the US Cloud
To configure access, please assign new values to the environment variables defining the proxy server used in the /etc/environment file:
-
https_proxyto define a proxy for the HTTPS protocol -
http_proxyto define a proxy for the HTTP protocol -
no_proxyto define the list of the resources proxy should not be used for
https_proxy and http_proxy values¶
Assign the <scheme>://<proxy_user>:<proxy_pass>@<host>:<port> string values to the https_proxy and http_proxy variables:
-
<scheme>defines the protocol used. It should match the protocol that the current environment variable sets up proxy for -
<proxy_user>defines the username for proxy authorization -
<proxy_pass>defines the password for proxy authorization -
<host>defines a host of the proxy server -
<port>defines a port of the proxy server
no_proxy value¶
To the no_proxy variable, assign the array of IP addresses and/or domains of the resources which proxy should not be used for:
-
127.0.0.1,127.0.0.8,127.0.0.9andlocalhostfor correct Wallarm node operation -
additional addresses in the format:
"<res_1>, <res_2>, <res_3>, <res_4>, ..."where<res_1>,<res_2>,<res_3>, and<res_4>are the IP addresses and/or domains
Example of the file /etc/environment¶
An example of the file /etc/environment below demonstrates the following configuration:
-
HTTPS and HTTP requests are proxied to the
1.2.3.4host with the1234port, using theadminusername and the01234password for authorization on the proxy server. -
Proxying is disabled for the requests sent to
127.0.0.1,127.0.0.8,127.0.0.9, andlocalhost.