Bookmarks tagged with #https.
Show all
Show all
TLS certificates for internal services done right
No self-signing headaches, no TLS erros.
Saved
on: 2026-07-09
Laravel, artisan serve, and HTTPS
How to serve your Laravel Project locally via HTTPS protocol
Saved
on: 2023-01-22
Why do we need HTTPS? - How HTTPS works
🙀 A cat explains how HTTPS works...in a comic! 😻
Tags:
#https
Saved
on: 2020-09-15
HTTP headers for the responsible developer - Twilio
Guide to using HTTP headers for a better web. Learn about HTTPS, HSTS, CSP, Cacheable, immutable resources, serving WebP images, Feature-Policy and more.
Saved
on: 2019-05-08
Certificates for localhost
Sometimes people want to get a certificate for the hostname “localhost”, either for use in local development, or for distribution with a native application that needs to communicate with a web application. Let’s Encrypt can’t provide certificates for “localhost” because nobody uniquely owns it, and it’s not rooted in a top level domain like “.com” or “.net”. It’s possible to set up your own domain name that happens to resolve to 127.
Saved
on: 2018-06-20
Remote Synthesis | Running SSL on localhost
Some strategies for local testing with SSL
Saved
on: 2018-04-24
Troy Hunt: The 6-Step "Happy Path" to HTTPS
It's finally time: it's time the pendulum swings further towards the "secure by
default" end of the scale than what it ever has before. At least insofar as
securing web traffic goes because as of this week's Chrome 62's launch, any
website with an input box is now doing this when served over an insecure
connection:
It's not doing it immediately for everyone
[https://textslashplain.com/2017/10/18/chrome-field-trials/], but don't worry,
it's coming very soon even if it hasn't yet arrived for yo
Saved
on: 2017-10-19
We need to talk about Session Tickets
More specifically, TLS 1.2 Session Tickets.
Session Tickets, specified in RFC 5077 [https://tools.ietf.org/html/rfc5077],
are a technique to resume TLS sessions by storing key material encrypted on the
clients. In TLS 1.2 they speed up the handshake from two to one round-trips.
Unfortunately, a combination of deployment realities and three design flaws
makes them the weakest link in modern TLS, potentially turning limited key
compromise into passive decryption of large amounts of traffic.
How
Saved
on: 2017-09-28
HTTPS on Stack Overflow: The End of a Long Road | Hacker News
Saved
on: 2017-05-22
Is TLS Fast Yet?
TLS has exactly one performance problem: it is not used widely enough. Everything else can be optimized.
Saved
on: 2016-01-31
What web developers should know about SSL but probably don't.
Saved
on: 2015-12-22
Why we don’t use a CDN: A story about SPDY and SSL (2014) | Hacker News
Saved
on: 2015-04-02
Why we don't use a CDN: A story about SPDY and SSL
Using a CDN was a forgone conclusion, as we assumed it would help us speed things up. But, after testing, we uncovered some surprising results.
Saved
on: 2015-04-02