anchor.diff:  The diagram below illustrates a HTTPS redirect loop and direct HTTP communication between a reverse proxy and an app server.
   
   <img src="../images/reverse-proxy.png">
  -
  -<hr>
   
   ### <a id='config-process'></a>Configure and push your app
   
  
positive.code: Use this website to create hashed username and password pairs for your website: 
  [http://www.htaccesstools.com/htpasswd-generator/](http://www.htaccesstools.com/htpasswd-generator/)
  
  ### <a id='force-https'></a>About FORCE_HTTPS with reverse proxies 
  
  If you are using a reverse proxy such as CloudFlare and you have rules to redirect HTTP, do not use FORCE_HTTPS. 
  This is because the reverse proxy is intended to communicate directly with the app through HTTP.
  
negative.code: 
  * **_Proxy support_** — Allows you to use a proxy to download dependencies during staging.
  
  * **_Force HTTPS_** — A way to enforce that all requests are sent via HTTPS. This redirects non-HTTPS requests as HTTPS requests. For information about when not to force HTTPS, see [About FORCE_HTTPS with Reverse Proxies](#force-https) below.
  
  ### <a id='basic-auth'></a>Creating hashes for basic authentication
  
  