Comment 4 for bug 1691749

The remaining issue is that the docs describe a method of deploying behind a proxy that will fail in a rather subtle way once no_proxy gets > 1024 chars, i.e when the number of IPs in the deployment reaches a surprisingly small number. That issue remains regardless of the merged patch. Is it legitimate to fail out if no_proxy (or indeed any env var) is too long?

However, the merged patch does provide a route to a successful deployment where a very short no_proxy string is defined in deployment_environment_variables. Introducing an alternative method for deploying behind a proxy in the documentation may be helpful.