Investigate slow page loads and check whether resources use HTTP/2 or HTTP/3. Measure the actual bottleneck, then recommend server or CDN changes where appropriate, explaining how shared connections and compressed headers affect loading.
- Investigating slow page loads
- Checking the HTTP protocol used for resources
- Reviewing web server or CDN settings
thedaviddias/Front-End-Checklist☆ 74.5KUpdated Oct 6, 2026
HTTP/2 protocol-specific attack playbook. Use when the target supports HTTP/2 and you need to exploit binary framing, HPACK compression, h2c upgrade smuggling, pseudo-header injection, stream multiplexing abuse, or H2→H1 downgrade translation flaws.
The English summary is being prepared. Showing the original description.
yaklang/hack-skills☆ 2.5KUpdated Sep 13, 2026
HTTP/2 protocol-specific attack playbook. Use when the target supports HTTP/2 and you need to exploit binary framing, HPACK compression, h2c upgrade smuggling, pseudo-header injection, stream multiplexing abuse, or H2→H1 downgrade translation flaws.
The English summary is being prepared. Showing the original description.
ShulkwiSEC/bb-huge☆ 23Updated Jul 11, 2026
Use when shared-IP HTTPS hosts serve the wrong application only on reused HTTP/2 connections—map DNS, SAN, SNI, :authority, listener, and backend ownership before applying 421.
The English summary is being prepared. Showing the original description.
mouadja02/skills☆ 10Updated Oct 17, 2026
HTTP Request Smuggling — frontend/backend HTTP parser uyumsuzluğunu sömürerek auth bypass, cache poisoning, internal endpoint erişimi
The English summary is being prepared. Showing the original description.
MustafaKemal0146/fetih☆ 5Updated Oct 11, 2026