You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/pages/04-web-development/41-https.markdown
+56-1Lines changed: 56 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,4 +8,59 @@ meta: The HTTP Secure (HTTPS) protocol encyrpts data between a web server and th
8
8
9
9
10
10
# HTTPS
11
-
The HTTP Secure (HTTPS) protocol encyrpts data between a web server and the client web browser.
11
+
The HTTP Secure (HTTPS) protocol encyrpts data between a web server and the
12
+
client web browser.
13
+
14
+
15
+
### HTTPS tutorials
16
+
*[How To Secure Nginx with Let's Encrypt on Ubuntu 18.04](https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-18-04)
17
+
walks through how to configure your [Nginx](/nginx.html) server with
18
+
HTTPS using a free [Let's Encrypt](https://letsencrypt.org/) domain
19
+
certificate.
20
+
21
+
*[Switching Your Site to HTTPS on a Shoestring Budget](https://css-tricks.com/switching-site-https-shoestring-budget/)
22
+
shows the steps for moving a GitHub Pages-based site or any site that
23
+
can be behind Cloudflare's free tier to HTTPS.
24
+
25
+
26
+
### HTTPS resources
27
+
*[The 6-Step "Happy Path" to HTTPS](https://www.troyhunt.com/the-6-step-happy-path-to-https/)
28
+
covers how to obtain a free SSL certificate, permanently redirect HTTP
29
+
to HTTPS and fix insecure references to non-HTTPS resources.
30
+
31
+
*[HTTPS on Stack Overflow: the end of a long road](https://nickcraver.com/blog/2017/05/22/https-on-stack-overflow/)
32
+
is a wonderfully in-depth post on transitioning from HTTP to HTTPS,
33
+
including redirecting all HTTP requests to HTTPS, for a very high
34
+
trafficked website.
35
+
36
+
*[TLS stats from 1.6 billion connections to mozilla.org](https://jve.linuxwall.info/blog/index.php?post/2016/08/04/TLS-stats-from-1.6-billion-connections-to-mozilla.org)
37
+
provides real-world data for which ciphersuites to use based on
38
+
mozilla.org connections.
39
+
40
+
*[How Let's Encrypt Works](https://letsencrypt.org/how-it-works/) is a
41
+
primer on how the free and now widely-used certificate service grants
42
+
and revokes domain certificates.
43
+
44
+
*[Performing & Preventing SSL Stripping: A Plain-English Primer](https://blog.cloudflare.com/performing-preventing-ssl-stripping-a-plain-english-primer/)
45
+
explains the KRACK Attack for stealing data despite an HTTPS connection
46
+
and how your site needs to use HSTS to prevent the attack.
47
+
48
+
*[HTTPS adoption has reached the tipping point](https://www.troyhunt.com/https-adoption-has-reached-the-tipping-point/)
49
+
shows data about the growth of HTTPS and how most sites now serve more
is a broad overview of documentation, community, pricing and other
186
+
notes for the major platforms as well as IBM OpenWhisk and
187
+
the [Fission.io](https://fission.io/) project.
188
+
189
+
*[Microsoft Azure Functions vs. Google Cloud Functions vs. AWS Lambda](https://cloudacademy.com/blog/microsoft-azure-functions-vs-google-cloud-functions-fight-for-serverless-cloud-domination-continues/)
190
+
presents an overview of Azure Functions and how they compare to
191
+
Google Cloud Functions and AWS Lambda.
192
+
193
+
172
194
### Serverless vendor lock-in?
173
195
There is some concern by organizations and developers about vendor lock-in
174
196
on serverless platforms. It is unclear if portability is worse for
@@ -183,13 +205,12 @@ perspectives on lock-in and using multiple cloud providers.
183
205
on that platform.
184
206
185
207
*[Why vendor lock-in with serverless isn’t what you think it is](https://medium.com/@PaulDJohnston/why-vendor-lock-in-with-serverless-isnt-what-you-think-it-is-d6be40fa9ca9)
186
-
is a short piece that also recommends using a single vendor for
187
-
now and stop worrying about hedging your bets because it typically
188
-
makes your infrastructure significantly more complex.
208
+
recommends using a single vendor for now and stop worrying about
209
+
hedging your bets because it typically makes your infrastructure
210
+
significantly more complex.
189
211
190
212
*[The (Fixable) Problem with Serverless](https://www.iopipe.com/2016/06/the-fixable-problem-with-serverless/)
191
213
is a bit of a marketing piece but it introduces
192
214
[the IOPipe open source projects](https://github.com/iopipe)
193
215
that are designed as an abstraction layer for running on multiple
0 commit comments