HTTP is a first-class citizen in Node.js, designed with streaming and low latency in mind. This makes Node.js well-suited for the foundation of a web library or framework.
The following defines the requirements to run the Node.js module in the Section platform:
process.env.PORTfor HTTP/1.1 — never using HTTPS or any other port.
next-hop:80as HTTP, never HTTPS.
next-hopresolves to the next proxy in the chain or the origin — whichever is next upstream.
X-Forwarded-Proto: httpsHTTP request header to perform HTTPS requests to the origin.
.gitignorefile which ignores the
package-lock.jsonfile which is generated by
yarnis unsupported for now.
X-Forwarded-Proto: httpsrequest header for HTTPS connections from the browser. Assume HTTP otherwise.
True-Client-IPrequest header containing the IP address of the client connecting to the Section servers. The
X-Forwarded-Forrequest header will be also be present but may contain multiple IP addresses from other HTTP proxies between the client and the Node.js module.