ult to False via API.resp_options. This lets you test your app locally with- out having to set up TLS. You can make this option configurable to easily switch between development and production environments serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol, for efficiently errors if the application does not start. Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s

fault to False via API.resp_options. This lets you test your app locally without having to set up TLS. You can make this option configurable to easily switch between development and production environments serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol [https://uwsgi- errors if the application does not start. Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s

serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol, for efficiently errors if the application does not start. Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s resp_options or falcon.asgi.App. resp_options. This lets you test your app locally without having to set up TLS. You can make this option configurable to easily switch between development and production environments

serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol, for efficiently errors if the application does not start. Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s resp_options or falcon.asgi.App. resp_options. This lets you test your app locally without having to set up TLS. You can make this option configurable to easily switch between development and production environments

serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol, for efficiently errors if the application does not start. Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s resp_options or falcon.asgi.App. resp_options. This lets you test your app locally without having to set up TLS. You can make this option configurable to easily switch between development and production environments

serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol, for efficiently errors if the application does not start. Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s resp_options or falcon.asgi.App. resp_options. This lets you test your app locally without having to set up TLS. You can make this option configurable to easily switch between development and production environments

serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol, for efficiently errors if the application does not start. Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s resp_options or falcon.asgi.App.resp_options. This lets you test your app locally without having to set up TLS. You can make this option configurable to easily switch between development and production environments

serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol, for efficiently errors if the application does not start. Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s resp_options or falcon.asgi.App.resp_options. This lets you test your app locally without having to set up TLS. You can make this option configurable to easily switch between development and production environments

serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol, for efficiently errors if the application does not start. Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s resp_options or falcon.asgi.App.resp_options. This lets you test your app locally without having to set up TLS. You can make this option configurable to easily switch between development and production environments

serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol, for efficiently Falcon Documentation, Release 3.1.0 Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s resp_options or falcon.asgi.App.resp_options. This lets you test your app locally without having to set up TLS. You can make this option configurable to easily switch between development and production environments