<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web-Security on it-learn.io | IT, Networking &amp; Cybersecurity Blog</title><link>https://blog.it-learn.io/tags/web-security/</link><description>Recent content in Web-Security on it-learn.io | IT, Networking &amp; Cybersecurity Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.it-learn.io/tags/web-security/index.xml" rel="self" type="application/rss+xml"/><item><title>SSL Stripping: Downgrading HTTPS to HTTP Without the User Noticing</title><link>https://blog.it-learn.io/posts/2026-05-01-ssl-stripping-downgrading-https-to-http/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://blog.it-learn.io/posts/2026-05-01-ssl-stripping-downgrading-https-to-http/</guid><description>&lt;p&gt;Moxie Marlinspike stood at the podium at Black Hat DC 2009 and demonstrated something that changed how the security community thought about HTTPS. The attack did not crack SSL. It did not exploit a cryptographic weakness. It exploited something far simpler: the gap between when a user types a domain name into their browser and when HTTPS is actually negotiated.&lt;/p&gt;
&lt;p&gt;That gap — the initial HTTP request — is all an attacker needs.&lt;/p&gt;</description></item></channel></rss>