<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TLS on Ivan Versluis — Networknet</title><link>https://networknet.nl/tags/tls/</link><description>Recent content in TLS on Ivan Versluis — Networknet</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 13 Nov 2026 10:14:31 +0100</lastBuildDate><atom:link href="https://networknet.nl/tags/tls/index.xml" rel="self" type="application/rss+xml"/><item><title>Trace an HTTPS request through the OSI model with curl</title><link>https://networknet.nl/snippets/curl-verbose-osi/</link><pubDate>Mon, 09 Nov 2026 12:00:00 +0100</pubDate><guid>https://networknet.nl/snippets/curl-verbose-osi/</guid><description>&lt;p>After more than 20 years in networking, I still use the seven-layer OSI model to structure a simple troubleshooting question: &lt;strong>at which layer does the connection stop?&lt;/strong>&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-sh" data-lang="sh">&lt;span class="line">&lt;span class="cl">curl -v --http1.1 https://example.com/
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Verbose output exposes several stages of an HTTPS request: hostname resolution, the TCP connection, TLS negotiation and certificate verification, followed by the HTTP request and response headers. Forcing HTTP/1.1 keeps the application exchange easy to recognise instead of negotiating HTTP/2.&lt;/p></description></item></channel></rss>