eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

197
active users

#http

1 post1 participant0 posts today
iRODS<p>iRODS Development Update: August 2025</p><p>Three intern presentations and four releases in a month!?</p><p><a href="https://irods.org/2025/08/irods-development-update-august-2025/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">irods.org/2025/08/irods-develo</span><span class="invisible">pment-update-august-2025/</span></a></p><p><a href="https://fosstodon.org/tags/irods" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>irods</span></a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>python</span></a> <a href="https://fosstodon.org/tags/pam" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pam</span></a> <a href="https://fosstodon.org/tags/java" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>java</span></a> <a href="https://fosstodon.org/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a> <a href="https://fosstodon.org/tags/s3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>s3</span></a> <a href="https://fosstodon.org/tags/interns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>interns</span></a></p>
iX Magazin<p>iX-Workshop API-Sicherheit: OWASP Top 10 API Security Risks</p><p>Lernen Sie hands-on, wie Sie Schwachstellen in der API-Implementierung vermeiden und Angriffe abwehren.</p><p><a href="https://www.heise.de/news/iX-Workshop-API-Sicherheit-OWASP-Top-10-API-Security-Risks-10539124.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&amp;utm_source=mastodon" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">heise.de/news/iX-Workshop-API-</span><span class="invisible">Sicherheit-OWASP-Top-10-API-Security-Risks-10539124.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&amp;utm_source=mastodon</span></a></p><p><a href="https://social.heise.de/tags/API" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>API</span></a> <a href="https://social.heise.de/tags/IdentityManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IdentityManagement</span></a> <a href="https://social.heise.de/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> <a href="https://social.heise.de/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IT</span></a> <a href="https://social.heise.de/tags/iXWorkshops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iXWorkshops</span></a> <a href="https://social.heise.de/tags/OWASP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OWASP</span></a> <a href="https://social.heise.de/tags/Schnittstellen" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Schnittstellen</span></a> <a href="https://social.heise.de/tags/Sicherheitsl%C3%BCcken" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sicherheitslücken</span></a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>news</span></a></p>
Hacker News 50<p>Show HN: Sping – An HTTP/TCP latency tool that's easy on the eye</p><p>Link: <a href="https://dseltzer.gitlab.io/sping/docs/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">dseltzer.gitlab.io/sping/docs/</span><span class="invisible"></span></a><br>Discussion: <a href="https://news.ycombinator.com/item?id=45008819" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">news.ycombinator.com/item?id=4</span><span class="invisible">5008819</span></a></p><p><a href="https://social.lansky.name/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a></p>
Script Kiddie<p><strong>Why are anime catgirls blocking my access to the Linux kernel?</strong></p> <p><a href="https://anonsys.net/display/bf69967c-3368-a6d6-f86d-bec306823413" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">anonsys.net/display/bf69967c-3</span><span class="invisible">368-a6d6-f86d-bec306823413</span></a></p>
Max Resing<p>Apparently, there exists a website called <code>ipv4[.]games</code>, where you can register HTTP web requests from hosts where you have access to. Once accessed, you can "claim" the requesting <a href="https://infosec.exchange/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> address with an <a href="https://infosec.exchange/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> GET request on <code>/claim?name=&lt;NAME&gt;</code>.</p><p>The leaderboard leads the person which claims most addresses of various <code>/8</code> networks.</p><p>It is wild to see partially 6-digit numbers for various <code>/8</code>s claimed by one and the same user.</p><p>My guess is: Either they leverage residential proxies, or leverage perhaps mass-spamming on having millions of people world-wide clicking links, or alternatively, leveraging modern software design to do the lookup for them (e.g. website previews on social media, or anti-phishing services that do a lookup, before they forward the mail to you).</p><p>No matter what, I am sure that millions of these IP addresses in there can be harvested as <a href="https://infosec.exchange/tags/open" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>open</span></a> <a href="https://infosec.exchange/tags/proxies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proxies</span></a> </p><p>Other than that, I like the idea, and love how gamification leads to some people developing creative ways on making millions of hosts on the Internet access this website. It probably still invites to unsolicited requests from strangers unknowingly participating in the game of a tech-savvy person.</p><p><a href="https://infosec.exchange/tags/Spamming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Spamming</span></a> <a href="https://infosec.exchange/tags/spoofing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>spoofing</span></a></p>
Wintermute_BBS<p>In Germany there we have this saying that talking about music is like dancing to architecture.</p><p>In a simillar way, I find it rather difficult to describe to people why I prefer coding in a language which is usually considererd one or all of the following: old / outdated / dead / feeding-to-a-niche / hard-to-understand - but I will give it a last try:</p><p>One of the things I like about the Forth programming language - in this case <a href="https://oldbytes.space/tags/esp32forth" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>esp32forth</span></a> - is that you can easily add hardware specific words from the Arduino library.</p><p>I was missing analogWrite, analogWriteFrequency and analogWriteResolution so I just added those.</p><p>But aside from that, using Forth on the ESP32 makes prototyping so much easier: you save yourself the endless cycle of "code, compile, upload, test, code..." since you can actually write your code interactively on the device (using either the Block Editor or the Visual Editor).</p><p>Being able to remotely connect to this development environment via either <a href="https://oldbytes.space/tags/Http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Http</span></a> or#Telnet just rounds it up for me.</p><p>Maybe it's because it brings me back to the times when I was coding BASIC on my bedsit, but maybe it really is because it is a very efficient way to code ... 🤷‍♂️ </p><p><a href="https://oldbytes.space/tags/Forth" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Forth</span></a> <br><a href="https://oldbytes.space/tags/ArduinoIDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ArduinoIDE</span></a> <br><a href="https://oldbytes.space/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Coding</span></a></p>
Vitex<p><a href="https://f.cz/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> <a href="https://f.cz/tags/Error" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Error</span></a> 418</p>
iX Magazin<p>iX-Workshop API-Sicherheit: OWASP Top 10 API Security Risks</p><p>Lernen Sie hands-on, wie Sie Schwachstellen in der API-Implementierung vermeiden und Angriffe abwehren.</p><p><a href="https://www.heise.de/news/iX-Workshop-API-Sicherheit-OWASP-Top-10-API-Security-Risks-10508412.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&amp;utm_source=mastodon" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">heise.de/news/iX-Workshop-API-</span><span class="invisible">Sicherheit-OWASP-Top-10-API-Security-Risks-10508412.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&amp;utm_source=mastodon</span></a></p><p><a href="https://social.heise.de/tags/API" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>API</span></a> <a href="https://social.heise.de/tags/IdentityManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IdentityManagement</span></a> <a href="https://social.heise.de/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> <a href="https://social.heise.de/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IT</span></a> <a href="https://social.heise.de/tags/iXWorkshops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iXWorkshops</span></a> <a href="https://social.heise.de/tags/OWASP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OWASP</span></a> <a href="https://social.heise.de/tags/Schnittstellen" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Schnittstellen</span></a> <a href="https://social.heise.de/tags/Sicherheitsl%C3%BCcken" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sicherheitslücken</span></a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>news</span></a></p>
Nicolas Fränkel 🇺🇦🇬🇪<p><a href="https://mastodon.top/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> is not simple</p><p><a href="https://daniel.haxx.se/blog/2025/08/08/http-is-not-simple/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">daniel.haxx.se/blog/2025/08/08</span><span class="invisible">/http-is-not-simple/</span></a></p>
Inautilo<p><a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Development</span></a> <a href="https://mastodon.social/tags/Pitfalls" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pitfalls</span></a><br>Server-side HTTP prioritization support · “Correct HTTP prioritization can’t always be relied upon.” <a href="https://ilo.im/165qa6" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ilo.im/165qa6</span><span class="invisible"></span></a></p><p>_____<br><a href="https://mastodon.social/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> <a href="https://mastodon.social/tags/HTTP2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP2</span></a> <a href="https://mastodon.social/tags/HTTP3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP3</span></a> <a href="https://mastodon.social/tags/Server" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Server</span></a> <a href="https://mastodon.social/tags/CDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CDN</span></a> <a href="https://mastodon.social/tags/Browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Browser</span></a> <a href="https://mastodon.social/tags/WebPerf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebPerf</span></a> <a href="https://mastodon.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DevOps</span></a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDev</span></a> <a href="https://mastodon.social/tags/Backend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Backend</span></a></p>
Hacker News 50<p>Ch.at – a lightweight LLM chat service accessible through HTTP, SSH, DNS and API</p><p>Link: <a href="https://ch.at/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ch.at/</span><span class="invisible"></span></a><br>Discussion: <a href="https://news.ycombinator.com/item?id=44849129" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">news.ycombinator.com/item?id=4</span><span class="invisible">4849129</span></a></p><p><a href="https://social.lansky.name/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a></p>
d0rk ✅<p><a href="https://m.youtube.com/watch?v=sslnkb4MnTg&amp;t=25152s&amp;pp=2AHAxAGQAgE%3D" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">m.youtube.com/watch?v=sslnkb4M</span><span class="invisible">nTg&amp;t=25152s&amp;pp=2AHAxAGQAgE%3D</span></a></p><p>Stream of James <a href="https://mastodon.social/tags/kettle" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kettle</span></a> <a href="https://mastodon.social/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a>/1.1 must die</p><p><a href="https://mastodon.social/tags/h1" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>h1</span></a> <a href="https://mastodon.social/tags/h2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>h2</span></a> <a href="https://mastodon.social/tags/defcon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>defcon</span></a> <a href="https://mastodon.social/tags/defcon33" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>defcon33</span></a></p>
kravietz 🦇<p>I’ve been thinking about this <a class="hashtag" href="https://agora.echelon.pl/tag/http" rel="nofollow noopener" target="_blank">#HTTP</a> 1.1 deprecation postulate and here are some random thoughts with no conclusion:</p><ul><li>Protocol deprecation in the web world is mostly driven by cryptography, because that’s a hard fact you can present to the business. Any argument that includes “potentially” and “low-risk” is automatically ignored.</li><li>The newest officially deprecated HTTP cryptographic protocol is TLS/1.1 introduced in 2006 and deprecated in 2021 (!). TLS 1.2 is 2008 and TLS 1.3 is 2018.</li><li>That in practice means anything that runs on TLS/1.2 - that is since 2008 - will be acceptable for business.</li><li>HTTP/2.0 was only introduced in 2015, that is <em>after</em> TLS 1.2, which means cryptography isn’t a “formal” trigger for upgrade to HTTP/2.0.</li><li>You only worry about backward compatibility on user-facing interfaces, so you could in theory get rid of HTTP/1.1 in all internal web stacks.</li><li>HTTP/2.0 <em>without</em> TLS is however a separate protocol (<code>h2c</code>) and some implementations miss support for plaintext HTTP/2.0 (intentionally, to get rid of plaintext HTTP).</li><li>But most backend stacks run on plaintext HTTP simply because there’s little point of running full-blown TLS between <code>localhost</code> and <code>localhost</code>.</li><li>So, migration from HTTP/1.1 to HTTP/2.0 in backend isn’t just matter of switching protocols - I’ve been there.</li></ul><p><a href="https://portswigger.net/blog/http-1-1-must-die-what-this-means-for-appsec-leadership" rel="nofollow noopener" target="_blank">https://portswigger.net/blog/http-1-1-must-die-what-this-means-for-appsec-leadership</a></p>
John Kristoff<p>Weekend Reads</p><p>* Societal cost of DDoS<br> <a href="https://thegfce.org/news/estimating-the-societal-cost-of-ddos-attacks-a-dual-lens-model-for-national-impact-assessment/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">thegfce.org/news/estimating-th</span><span class="invisible">e-societal-cost-of-ddos-attacks-a-dual-lens-model-for-national-impact-assessment/</span></a><br>* HTTP/1.1 desync attacks<br> <a href="https://portswigger.net/research/http1-must-die" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">portswigger.net/research/http1</span><span class="invisible">-must-die</span></a><br>* Internet broadband in Nigeria<br> <a href="https://spectrum.ieee.org/broadband-internet-in-nigeria" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">spectrum.ieee.org/broadband-in</span><span class="invisible">ternet-in-nigeria</span></a><br>* AS to org mapping from metadata<br> <a href="https://arxiv.org/abs/2508.02571" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">arxiv.org/abs/2508.02571</span><span class="invisible"></span></a><br>* Flow control for high-speed nets<br> <a href="https://dipsingh.github.io/FlowControl-HighSpeed-Networks/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dipsingh.github.io/FlowControl</span><span class="invisible">-HighSpeed-Networks/</span></a></p><p><a href="https://infosec.exchange/tags/DDoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DDoS</span></a> <a href="https://infosec.exchange/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> <a href="https://infosec.exchange/tags/Nigeria" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Nigeria</span></a> <a href="https://infosec.exchange/tags/BGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BGP</span></a> <a href="https://infosec.exchange/tags/FlowControl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FlowControl</span></a></p>
Nils Goroll 🕊️:varnishcache:<p>uefi can boot over http/4 and http/6 😂</p><p><a href="https://infosec.exchange/@shodansafari/114980055705377524" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">infosec.exchange/@shodansafari</span><span class="invisible">/114980055705377524</span></a> <a href="https://fosstodon.org/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a> <a href="https://fosstodon.org/tags/shitpost" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>shitpost</span></a></p>
Tommi 🤯<p><strong>Can’t connect to public WiFi via Linux</strong></p><p>I am using Fedora 42, and I am unable to access the captive portal of inOui TGV. I can connect to the WiFi with no problems, but I can’t get access to the Internet.</p><p>I have tried <strong>everything</strong>:</p><ol><li>Connecting to <code>192.168.1.1</code>, to <code>http://neverssl.com</code>, to <code>http://wifi.sncf</code> via browser</li><li>Running <code>sudo dhclient -r</code> and rebooting the device</li><li>Running <code>systemctl restart NetworkManager</code></li><li>Also other stuff I tried in the past with other public WiFis. I am sure there is something wrong with my specific device configuration, it’s not this network.</li></ol><p>Nothing works 😩</p><p>Can somebody who understands this stuff help me?</p><p><a href="https://pan.rent/tags/help" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>help</span></a> <a href="https://pan.rent/tags/mastoAiuto" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastoAiuto</span></a> <a href="https://pan.rent/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://pan.rent/tags/LinuxNetwork" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxNetwork</span></a> <a href="https://pan.rent/tags/Network" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Network</span></a> <a href="https://pan.rent/tags/CaptivePortal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CaptivePortal</span></a> <a href="https://pan.rent/tags/WiFi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WiFi</span></a> <a href="https://pan.rent/tags/PublicWiFi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PublicWiFi</span></a> <a href="https://pan.rent/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> <a href="https://pan.rent/tags/HTTPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTPS</span></a> <a href="https://pan.rent/tags/troubleshoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>troubleshoot</span></a> <a href="https://pan.rent/tags/LinuxHelp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxHelp</span></a> <a href="https://pan.rent/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fedora</span></a> <a href="https://pan.rent/tags/Fedora42" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fedora42</span></a></p>
Leon Brocard<p>Anyone else using Compression Dictionary Transport to compress response bodies with a site-specific dictionary?<br>The first time you visit <a href="https://www.astray.com/recipes/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">astray.com/recipes/</span><span class="invisible"></span></a> in Chrome, the response body is compressed with Brotli and takes 2,186 bytes. In the background the browser downloads a 400 byte dictionary.<br>The next time you visit <a href="https://www.astray.com/recipes/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">astray.com/recipes/</span><span class="invisible"></span></a> the body is compressed with Brotli (using the shared dictionary) and takes only 1,799 bytes.<br>The savings add up with each request.<br><a href="https://fosstodon.org/tags/webperf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webperf</span></a> <a href="https://fosstodon.org/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a></p>
Beady Belle Fanchannel<p>In my side-project I send the &lt;head&gt; element within the first ~10ms, meaning the browser can start fetching more resources immediately (it also fits the first TCP packet).</p><p>Is this a common thing to do? If not, why not?</p><p><a href="https://mastodon.xyz/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a> <a href="https://mastodon.xyz/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a></p>
John Kristoff<p>Weekend Reads</p><p>* URI redirection patterns <a href="https://arxiv.org/abs/2507.22019" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">arxiv.org/abs/2507.22019</span><span class="invisible"></span></a><br>* AI and college grad jobs <a href="https://www.wsj.com/lifestyle/careers/ai-entry-level-jobs-graduates-b224d624?st=vM9BGX" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">wsj.com/lifestyle/careers/ai-e</span><span class="invisible">ntry-level-jobs-graduates-b224d624?st=vM9BGX</span></a><br>* Internet control in Russia <a href="https://www.hrw.org/report/2025/07/30/disrupted-throttled-and-blocked/state-censorship-control-and-increasing-isolation" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">hrw.org/report/2025/07/30/disr</span><span class="invisible">upted-throttled-and-blocked/state-censorship-control-and-increasing-isolation</span></a><br>* SNI-based QUIC censorship in China <a href="https://gfw.report/publications/usenixsecurity25/en/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gfw.report/publications/usenix</span><span class="invisible">security25/en/</span></a><br>* Running a certificate transparency log <a href="https://ipng.ch/s/articles/2025/07/26/certificate-transparency-part-1/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ipng.ch/s/articles/2025/07/26/</span><span class="invisible">certificate-transparency-part-1/</span></a></p><p><a href="https://infosec.exchange/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> <a href="https://infosec.exchange/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://infosec.exchange/tags/Censorship" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Censorship</span></a> <a href="https://infosec.exchange/tags/Russia" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Russia</span></a> <a href="https://infosec.exchange/tags/QUIC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>QUIC</span></a> <a href="https://infosec.exchange/tags/China" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>China</span></a> <a href="https://infosec.exchange/tags/X509" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>X509</span></a></p>
Tom :damnified:<p>Remember when I published the metalhead.club anthem on <a href="https://music.metalhead.club" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">music.metalhead.club</span><span class="invisible"></span></a>, some users couldn't access the page and got an error message? </p><p>Until a week ago, I couldn't explain the error. </p><p>Now I can! You can read about where the error comes from and what my fix looks like on my blog: </p><p>“Nginx HTTP/3 proxy server displays content from the wrong virtual host” - <a href="https://thomas-leister.de/en/nginx-http3-quic-proxy-wrong-virtual-host/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">thomas-leister.de/en/nginx-htt</span><span class="invisible">p3-quic-proxy-wrong-virtual-host/</span></a></p><p><a href="https://metalhead.club/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nginx</span></a> <a href="https://metalhead.club/tags/quic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>quic</span></a> <a href="https://metalhead.club/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a> <a href="https://metalhead.club/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nginx</span></a> <a href="https://metalhead.club/tags/webserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webserver</span></a> <a href="https://metalhead.club/tags/server" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>server</span></a></p>