lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

60
active users

#http

0 posts0 participants0 posts today
Bradley Taunt<p>Updated my httpd.rocks guide with a small section about implementing Basic HTTP Authentication:</p><p><a href="https://httpd.rocks/#http-basic-authentication" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">httpd.rocks/#http-basic-authen</span><span class="invisible">tication</span></a></p><p><a href="https://mastodon.bsd.cafe/tags/httpd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>httpd</span></a> <a href="https://mastodon.bsd.cafe/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openbsd</span></a> <a href="https://mastodon.bsd.cafe/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a></p>
Benjamin<p>Recently seen a rant about how FOSS devs should stop naming things because "eks em pee pee" is a terrible name.</p><p>I guess "eidj titty pee" is out as well then.</p><p><a href="https://toot.berlin/tags/RandomThought" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RandomThought</span></a> <a href="https://toot.berlin/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XMPP</span></a> <a href="https://toot.berlin/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</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>
Gea-Suan Lin<p><a href="https://blog.gslin.org/archives/2025/08/16/12575/stardict-%e9%a0%90%e8%a8%ad%e6%9c%83%e5%b0%87%e5%89%aa%e8%b2%bc%e7%b0%bf%e7%9a%84%e5%85%a7%e5%ae%b9%e9%80%8f%e9%81%8e-http-%e4%b8%8d%e6%98%af-https-%e5%82%b3%e5%88%b0%e4%b8%ad%e5%9c%8b%e7%9a%84/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.gslin.org/archives/2025/0</span><span class="invisible">8/16/12575/stardict-%e9%a0%90%e8%a8%ad%e6%9c%83%e5%b0%87%e5%89%aa%e8%b2%bc%e7%b0%bf%e7%9a%84%e5%85%a7%e5%ae%b9%e9%80%8f%e9%81%8e-http-%e4%b8%8d%e6%98%af-https-%e5%82%b3%e5%88%b0%e4%b8%ad%e5%9c%8b%e7%9a%84/</span></a></p><p>StarDict 預設會將剪貼簿的內容透過 HTTP (不是 HTTPS) 傳到中國的伺服器上</p><p><a href="https://abpe.org/tags/china" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>china</span></a> <a href="https://abpe.org/tags/chinese" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chinese</span></a> <a href="https://abpe.org/tags/clipboard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clipboard</span></a> <a href="https://abpe.org/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a> <a href="https://abpe.org/tags/https" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>https</span></a> <a href="https://abpe.org/tags/malicious" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malicious</span></a> <a href="https://abpe.org/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> <a href="https://abpe.org/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> <a href="https://abpe.org/tags/stardict" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>stardict</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>
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>
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>
Kushal Das :python: :tor: 🇸🇪<p>In <a href="https://toots.dgplug.org/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a> / <a href="https://toots.dgplug.org/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rustlang</span></a> I have a <a href="https://toots.dgplug.org/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> endpoint (<a href="https://toots.dgplug.org/tags/actix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>actix</span></a>) , where for a given query, it fetches <a href="https://toots.dgplug.org/tags/JWT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JWT</span></a> from the given parameter (URLS) and validates, puts some logic and returns the result. How to write unittest for this care in rust?</p>
Orhun Parmaksız 👾<p>This is one of the best terminal API clients out there right now 💯</p><p>📡 **ATAC** — Postman-like client but in your terminal</p><p>🖼️ Recently added image support!</p><p>🦀 Written in Rust &amp; built with <span class="h-card" translate="no"><a href="https://fosstodon.org/@ratatui_rs" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ratatui_rs</span></a></span></p><p>⭐ GitHub: <a href="https://github.com/Julien-cpsn/ATAC" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/Julien-cpsn/ATAC</span><span class="invisible"></span></a></p><p><a href="https://fosstodon.org/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rustlang</span></a> <a href="https://fosstodon.org/tags/ratatui" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ratatui</span></a> <a href="https://fosstodon.org/tags/tui" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tui</span></a> <a href="https://fosstodon.org/tags/postman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>postman</span></a> <a href="https://fosstodon.org/tags/api" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>api</span></a> <a href="https://fosstodon.org/tags/client" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>client</span></a> <a href="https://fosstodon.org/tags/terminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>terminal</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/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>testing</span></a></p>
Dendrobatus Azureus<p>A recent research has exposed more than 40 * 10³ IoT cameras happily showing their feed _and_ location to anyone who can browse and use search engines specialized in the indexing of the misconfigured devices.</p><p>More than 14 * 10³ are localised in the USA.</p><p>Read more here.</p><p>Note: <br>I know that there are more than a million of these cameras world wide misconfigured an open on just port 80 http not even TLS 443, with admin / admin as credentials 🪪 </p><p><a href="https://www.theregister.com/2025/06/10/40000_iot_cameras_exposed/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">theregister.com/2025/06/10/400</span><span class="invisible">00_iot_cameras_exposed/</span></a></p><p><a href="https://mastodon.bsd.cafe/tags/Infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Infosec</span></a> <a href="https://mastodon.bsd.cafe/tags/nightmare" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nightmare</span></a> <a href="https://mastodon.bsd.cafe/tags/not" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>not</span></a> <a href="https://mastodon.bsd.cafe/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>news</span></a> <a href="https://mastodon.bsd.cafe/tags/IoT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IoT</span></a> <a href="https://mastodon.bsd.cafe/tags/cameras" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cameras</span></a> <a href="https://mastodon.bsd.cafe/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> <a href="https://mastodon.bsd.cafe/tags/misconfigured" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>misconfigured</span></a> <a href="https://mastodon.bsd.cafe/tags/streaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>streaming</span></a> <a href="https://mastodon.bsd.cafe/tags/TLS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TLS</span></a> <a href="https://mastodon.bsd.cafe/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a></p>
heise online<p>Missing Link: Tim Berners-Lee wird 70 – der Architekt des World Wide Webs</p><p>Der Mann, der uns das WWW schenkte, feiert 70. Geburtstag und kämpft weiter für ein freies Netz. Ein Blick auf sein technisches Erbe und seine aktuellen Pläne.</p><p><a href="https://www.heise.de/news/Missing-Link-Tim-Berners-Lee-wird-70-der-Architekt-des-World-Wide-Webs-10436837.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/Missing-Link-Tim</span><span class="invisible">-Berners-Lee-wird-70-der-Architekt-des-World-Wide-Webs-10436837.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/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</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/Internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Internet</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/MissingLink" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MissingLink</span></a> <a href="https://social.heise.de/tags/Netzpolitik" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Netzpolitik</span></a> <a href="https://social.heise.de/tags/Wissenschaft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wissenschaft</span></a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>news</span></a></p>
Nelson<p>As Mozilla fumbles <a href="https://jawns.club/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Firefox</span></a>, let's reflect on what we'd lose if this unique browser + engine dies.</p><p>How can I get a list of <a href="https://jawns.club/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a>, <a href="https://jawns.club/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</span></a> and <a href="https://jawns.club/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSS</span></a> features that are only supported by Firefox / <a href="https://jawns.club/tags/Gecko" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gecko</span></a>? Does caniuse.com or MDN have this? Wikipedia?</p><p>Only Firefox supports assigning <a href="https://jawns.club/tags/stylesheets" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>stylesheets</span></a> through HTTP headers:<br><a href="https://meiert.com/blog/prefer-http-headers/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">meiert.com/blog/prefer-http-he</span><span class="invisible">aders/</span></a></p><p>Only Firefox supports alternate stylesheets: <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/rel/alternate_stylesheet" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">developer.mozilla.org/en-US/do</span><span class="invisible">cs/Web/HTML/Reference/Attributes/rel/alternate_stylesheet</span></a></p><p>Put these facts together, and you can make a secret stylesheet only for Firefox users.</p>
Andrey DarkCat09<p>Try it out<br><code>curl -X MEOW https://dc09.ru</code><br><code>curl -X HELLO https://dc09.ru</code><br><code>curl -X HUG https://dc09.ru | sh -</code><br><code>curl -X PAT https://dc09.ru | sh -</code></p><p>Config snippet is <a href="https://git.dc09.ru/DarkCat09/nginx-configs/src/branch/main/s/methods" rel="nofollow noopener" target="_blank">here</a>, supposed to be placed in a <code>server{}</code> block (but I don't think you want to set it up for yourself).</p><p>Image displaying shell script is <a href="https://git.dc09.ru/DarkCat09/imgsh/src/branch/main/img.sh" rel="nofollow noopener" target="_blank">this one</a>, even supports Android.</p><p><a href="https://gts.dc09.ru/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nginx</span></a> <a href="https://gts.dc09.ru/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a> <a href="https://gts.dc09.ru/tags/dc09ru" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dc09ru</span></a></p>
Deni Mintsaev 🇪🇺<p><span class="h-card" translate="no"><a href="https://mastodon.social/@kyrylosilin" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kyrylosilin</span></a></span> My totally serious response to justfuckingusehtml.com:</p><p>curl <a href="https://justfuckingusehttp.com" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">justfuckingusehttp.com</span><span class="invisible"></span></a><br>(the URL has to have https://, Mastodon just doesn't display it...)</p><p>On Windows you can use this command:<br>(Invoke-WebRequest <a href="https://justfuckingusehttp.com/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">justfuckingusehttp.com/</span><span class="invisible"></span></a>).Content</p><p><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/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coding</span></a> <a href="https://mastodon.social/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>frontend</span></a> <a href="https://mastodon.social/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>html</span></a> <a href="https://mastodon.social/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a></p>
iX Magazin<p>iX-Workshop: API-Design und -Entwicklung mit HTTP, REST und OpenAPI</p><p>Lernen Sie, wie man effiziente und benutzerfreundliche APIs entwickelt, HTTP- und REST-Standards anwendet und standardisierte Referenzdokumentationen erstellt.</p><p><a href="https://www.heise.de/news/iX-Workshop-API-Design-und-Entwicklung-mit-HTTP-REST-und-OpenAPI-10373876.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">Design-und-Entwicklung-mit-HTTP-REST-und-OpenAPI-10373876.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/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/Softwareentwicklung" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Softwareentwicklung</span></a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>news</span></a></p>
KSev 🇳🇴🌻🚲 :donor:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@404mediaco" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>404mediaco</span></a></span> Found a genuine 404 moment! <br>But “Not found” <a href="https://infosec.exchange/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a></p>

RFCs you should probably read if you're bug hunting modern stacks:

* RFC 8820: URI Design and Ownership
* RFC 8725: JSON Web Token Best Current Practices
* RFC 9110: HTTP Semantics
* RFC 9111: HTTP Caching
* RFC 9112: HTTP/1.1
* RFC 9113: HTTP/2
* RFC 9114: HTTP/3

Also worth a read:

* RFC 7230: Message Syntax and Routing
* RFC 7231: Semantics and Content
* RFC 7232: Conditional Requests
* RFC 7233: Range Requests
* RFC 7234: Caching
* RFC 7235: Authentication

#research, #exploitation, #http