Skip to content

Configuring reverse proxy for Industrial Edge Devices

Industrial Edge Devices leverage a reverse proxy to forward requests to various services, including applications. This setup enhances system integration and efficiency. In this tutorial, you will learn how to configure the reverse proxy for optimal performance and seamless integration.

Optimizing performance and resource usage for mixed file sizes

If your application serves a mix of small and large files, optimizing for both performance and resource usage is crucial. As an App Developer, you can fine-tune your reverse proxy configuration by adjusting specific proxy_* headers based on your use cases.

Below are some options to consider:

  • Use proxy_buffering: This setting can enhance performance and reduce backend load by buffering responses in memory. Enable this if memory availability is not a constraint in your environment.
  • Use proxy_max_temp_file_size: This setting helps in efficiently managing disk usage and handling large responses. Adjust this parameter to control the maximum size of temporary files used for buffering responses to disk.

Choose the configuration that best fits your specific needs to achieve optimal performance and resource management for your application.

Reserved paths

When developing applications for the platform, certain paths are reserved for system services. Using these paths in your application can cause conflicts, potentially disrupting core functionality (e.g., remote access to the device). To ensure smooth operation and compatibility, app developers must avoid using the reserved paths listed below:

/tunnel
/device/edge
/firmwaremanagement
/ws
/v2
/ems
/p.service
/csrf/generate
/vouch/logout
/pp
/auth
/osbar
/launchpad
/assets
/iem-ui
/admin/api
/portal/api
/myadmin/secure/px
/a.service
/licensing-service
/state-service
/iess-storage
/devicetypemanagement
/firmwaremanager
/firmwaredeployment
/api/wfx
/metrics
/webui
/api/iemaab-api
/db
/mqtt-connector/api
/mqtt-connector-ui
/sa-config-api
/opcua-config-ui
/opcua/api
/cc
/cloud-connector
/dataxess-ui
/dataxess/api
/sfc
/flow-creator

Potential impact of using reserved paths

If your application uses any of the reserved paths above, you may experience the following issues:

  • Remote access disruptions: The application may not be accessible via the remote access to the device (tunnel service)
  • Conflict with system services: System functionalities might be impaired, leading to unpredictable behavior