Merge pull request #155 from AxisCommunications/sync-20241210-1

Update proxy page (#359)

Author: pataxis

docs/acap-sdk-version-3/develop-applications/vapix-access-for-acap-applications.md

@@ -108,7 +108,7 @@ After obtaining the credentials, it's ready to make the actual VAPIX call. The A
 
 > - **NOTE** If the device has set global device proxy, reaching the local virtual host (127.0.0.12)
 > is only possible if 127.0.0.12 is added to the `No proxy` list, as described in
-> [Configure-global-device-proxy](./global-device-proxy#configure-global-device-proxy).
+> [Configure global device proxy](../../develop/proxy#configure-global-device-proxy).
 
 1. Define a VAPIX endpoint:
 

docs/api/native-sdk-api.md

@@ -541,7 +541,7 @@ The Jansson API was introduced in Native SDK 1.14.
 
 ## Curl
 
-Open-source library for transferring data with URLs. See [curl documentation](https://curl.se/docs/). For proxy configuration see [Global device proxy](../develop/global-device-proxy).
+Open-source library for transferring data with URLs. See [curl documentation](https://curl.se/docs/). For proxy configuration see [Global device proxy](../develop/proxy).
 
 ### Compatibility
 

docs/develop/VAPIX-access-for-ACAP-applications.md

@@ -101,7 +101,7 @@ After obtaining the credentials, it's ready to make the actual VAPIX call. The A
 
 > - **NOTE** If the device has set global device proxy, reaching the local virtual host (127.0.0.12)
 > is only possible if 127.0.0.12 is added to the `No proxy` list, as described in
-> [Configure-global-device-proxy](./global-device-proxy#configure-global-device-proxy).
+> [Configure global device proxy](./proxy#configure-global-device-proxy).
 
 1. Define a VAPIX endpoint:
 

docs/develop/global-device-proxy.md

@@ -0,0 +1,49 @@
+---
+layout: page
+parent: Develop ACAP applications
+title: Proxy
+nav_order: 11
+---
+
+# Proxy
+
+## Proxy in build time
+
+The ACAP Native SDK build environment use Docker and if the build machine
+is positioned inside a network with proxy, the Docker toolchain needs to be
+configured.
+
+### Docker daemon proxy
+
+To enable pull of ACAP Native SDK images from Docker Hub in a network with
+proxy, the Docker daemon needs to be configured. For instructions see
+<https://docs.docker.com/engine/daemon/proxy>.
+
+### Docker build environment
+
+The build instruction of ACAP applications is defined in the `Dockerfile` and if
+the application build tries to connect to external resources such as installing
+Ubuntu packages via `apt` or downloading files via `curl` in a network with
+proxy, the Docker CLI needs to be configured. For instructions see
+<https://docs.docker.com/engine/cli/proxy>.
+
+## Proxy in runtime
+
+To make an ACAP application use a proxy during runtime, it's possible to
+configure a global device proxy. Global device proxy settings act as global
+environment variables in AXIS OS. There are three types of global device
+proxies that can be configured; `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY`.
+
+### Configure global device proxy
+
+Global device proxy can be set via either:
+
+- The VAPIX
+  [Network Settings API](https://developer.axis.com/vapix/network-video/network-settings-api#setglobalproxyconfiguration-1).
+- The network page at `http://<AXIS_DEVICE_IP>/index.html#system/network` and
+  section `Global proxies`.
+
+### How are ACAP applications affected?
+
+ACAP applications can be affected by global device proxy if they use the curl
+API or in any other way are able to pick up proxy from environment variables.