Some clients reported problems when the MENU app was accessed via web from within corporate networks (e.g. banks, insurance, government). Tests from within some corporate networks confirmed that:
- calls to our hosted domain (menu.app and the client domain) was ok
- 3rd party domains called by the webapp were partially blocked (e.g. Google for maps, Amazon for assets on S3 etc.)
This led to problems when registering or when ordering.
Many bigger companies have open proxies (aka outbound, outgoing, forwarding proxies) installed that filter the outgoing internet traffic by content or by target domain. With such an approach, they try to either prevent data leakage or to ensure employee performance.
With the recent introduction of the Foodspot functionality, MENU app is more frequently used from within such corporate networks.
The solution is to configure the filtering correctly in a way that the MENU client application can access all resources needed. Normally, these companies provide forms or a defined process for their employees to exclude such non-critical external resources.
However, in many cases this will not be possible. If the filtering is based on the target domain, there is a high probability that domains such as google.com, amazon.com or facebook.com are filtered for other reasons and can not be excluded just for accessing MENU.
As a workaround, users can order with the mobile or web app using a private network, e.g. directly connecting to a public telecom carrier and not using the restricted network of their employer.