✳flâneur — a map of the web's best reading

About HTTPS - FastAPI

fastapi.tiangolo.com · 2,088 words · saved by 1 readers

If you are in a hurry or don't care, continue with the next sections for step by step instructions to set everything up with different techniques. To learn the basics of HTTPS, from a consumer perspective, check https://howhttps.works/. Now, from a developer's perspective, here are several things to have in mind while thinking about HTTPS: It is a common practice to have one program/HTTP server running on the server (the machine, host, etc.) and managing all the HTTPS parts: receiving the encrypted HTTPS requests, sending the decrypted HTTP requests to the actual HTTP application running in the same server (the FastAPI application, in this case), take the HTTP response from the application, encrypt it using the appropriate HTTPS certificate and sending it back to the client using HTTPS. This server is often called a TLS Termination Proxy. Some of the options you could use as a TLS Termination Proxy are: Before Let's Encrypt, these HTTPS certificates were sold by trusted third parties.

About HTTPS ¶ It is easy to assume that HTTPS is something that is just "enabled" or not. But it is way more complex than that. Tip If you are in a hurry or don't care, continue with the next sections for step by step instructions to set everything up with different techniques. To learn the basics of HTTPS , from a consumer perspective, check https://howhttps.works/ . Now, from a developer's perspective , here are several things to keep in mind while thinking about HTTPS: For HTTPS, the server needs to have "certificates" generated by a third party . Those certificates are actually acquir

Explore this link on the map →

related reading