WhatsApp-Channel don't use outgoing http-proxy when communicating to meta

[byPARSE]

Used Zammad Version

6.3.1

Environment

• Installation method: on prem
• Operating system (if you're unsure: cat /etc/os-release ): not relevant
• Database + version: not relevant
• Elasticsearch version: not relevant
• Browser + version: not relevant

Actual behaviour

The WhatsApp-Channel communicate to Meta (graph.facebook.com) without using the proxy-settings set under Settings->System->Network.

Expected behaviour

When proxy is set all the http/s protocol using-modules have to use the proxy for outgoing communication. In hardened environments the out-/incoming network-communication has to go exactly-predefined ways.

Steps to reproduce the behaviour

Setup WA-Channel, set a valid proxy under Settings->System->Network and use tcp-sniffers like tcpdump to see that the outgoing communication for WA don't use the set proxy.

Support Ticket

Ticket#10160841

I'm sure this is a bug and no feature request or a general question.

no

[tschaefer]

The named setting is only evaluated by an internal library.

@byPARSE You can verify that TLS proxying for a WA channel is working in general by setting the environment http_proxy on Zammad start.

[tschaefer]

Setting the environment variable http_proxy fixes the issue (confirmed by the client, see Ticket#161109).

Zammad should evaluate the named environment variables http_proxy, https_proxy, and no_proxy. These values should take precedence over the internal settings. The internal settings are not suitable for third-party libraries - hen egg problem.