<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Http — Pingiskok</title><link>https://rmrf.tips/en/tags/http/</link><description>Bugs, vulnerabilities and security research. Web2, Web3, Bug Bounty</description><generator>Hugo</generator><language>en</language><managingEditor>rmrf_0</managingEditor><webMaster>rmrf_0</webMaster><copyright>&#169; 2026 Pingiskok</copyright><lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0300</lastBuildDate><atom:link href="https://rmrf.tips/en/tags/http/index.xml" rel="self" type="application/rss+xml"/><item><title>Web servers, Part 2: what happens to a request inside nginx and Apache</title><link>https://rmrf.tips/en/series/web-servers/web-servers-anatomy/</link><pubDate>Sat, 24 Oct 2026 00:00:00 +0300</pubDate><guid>https://rmrf.tips/en/series/web-servers/web-servers-anatomy/</guid><description>How nginx and Apache select a site, process the path and forward a request to the application, and what you can test from the outside.</description></item><item><title>Web servers, Part 1: where HTTP actually breaks</title><link>https://rmrf.tips/en/series/web-servers/web-servers-why-broken/</link><pubDate>Sat, 24 Oct 2026 00:00:00 +0300</pubDate><guid>https://rmrf.tips/en/series/web-servers/web-servers-why-broken/</guid><description>How proxies and applications interpret the same request differently: body boundaries, paths, forwarding headers and cache keys.</description></item></channel></rss>