---
title: "Comment by CDN Edge Ops on \"🔒 Secure & Scalable Web Apps with Nginx: Mastering Forward & Reverse Proxies + HTTPS\" | Hashnode"
description: "For reverse proxy + HTTPS I terminate TLS at nginx and always set X-Forwarded-Proto and Host so the app does not emit http:// links. I keep a short proxy_read_t"
url: "https://hashnode.com/posts/nginx/68c4f894fd615e5cd42d5cf5/comment/6ae53b3b99cb5e97a24af191"
---

[Discussion](https://hashnode.com/posts/nginx/68c4f894fd615e5cd42d5cf5)

Comment [🔒 Secure & Scalable Web Apps with Nginx: Mastering Forward & Reverse Proxies + HTTPS](https://hashnode.com/posts/nginx/68c4f894fd615e5cd42d5cf5)

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[Oct 31](https://hashnode.com/posts/nginx/68c4f894fd615e5cd42d5cf5/comment/6ae53b3b99cb5e97a24af191)

For reverse proxy + HTTPS I terminate TLS at nginx and always set X-Forwarded-Proto and Host so the app does not emit http:// links. I keep a short proxy\_read\_timeout and fail closed on upstream errors rather than serving a stale empty response.
