digitalcourage.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Diese Instanz wird betrieben von Digitalcourage e.V. für die Allgemeinheit. Damit wir das nachhaltig tun können, erheben wir einen jährlichen Vorausbeitrag von 1€/Monat per SEPA-Lastschrifteinzug.

Server stats:

812
active users

#http

9 posts9 participants0 posts today

🦖 Set-Cookie header
✅ Widely available (from Jul 2015)

developer.mozilla.org/en-US/do

The HTTP Set-Cookie response header is used to send a cookie from the server to the user agent, so that the user agent can send it back to the server later. To send multiple cookies, multiple Set-Cookie headers should be sent in the same response.

The MDN Web Docs logo, featuring a blue accent color, displayed on a solid black background.
MDN Web DocsSet-Cookie header - HTTP | MDNThe HTTP Set-Cookie response header is used to send a cookie from the server to the user agent, so that the user agent can send it back to the server later. To send multiple cookies, multiple Set-Cookie headers should be sent in the same response.

Apparently, there exists a website called ipv4[.]games, where you can register HTTP web requests from hosts where you have access to. Once accessed, you can "claim" the requesting #IPv4 address with an #HTTP GET request on /claim?name=<NAME>.

The leaderboard leads the person which claims most addresses of various /8 networks.

It is wild to see partially 6-digit numbers for various /8s claimed by one and the same user.

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).

No matter what, I am sure that millions of these IP addresses in there can be harvested as #open #proxies

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.

In Germany there we have this saying that talking about music is like dancing to architecture.

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:

One of the things I like about the Forth programming language - in this case #esp32forth - is that you can easily add hardware specific words from the Arduino library.

I was missing analogWrite, analogWriteFrequency and analogWriteResolution so I just added those.

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).

Being able to remotely connect to this development environment via either #Http or #Telnet just rounds it up for me.

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 ... 🤷‍♂️

#Forth
#ArduinoIDE
#Coding

release: webServer tool for linux

JS is the language of the web. But afaik, Quickjs didn't have a HTTP server module yet, so I did the plumbing and created Mongoose-qjs.

wget cce.citiwise.eu/downloads/qjs-webserver-0.2.4.tgz

sha256sum
d33a6a31c448bf6d61d0a15a8c61ec1bb1b2708768eef3bafe23eecb47192427

#qjs #linux #x86-64 #http

I’ve been thinking about this #HTTP 1.1 deprecation postulate and here are some random thoughts with no conclusion:

  • 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.
  • 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.
  • That in practice means anything that runs on TLS/1.2 - that is since 2008 - will be acceptable for business.
  • HTTP/2.0 was only introduced in 2015, that is after TLS 1.2, which means cryptography isn’t a “formal” trigger for upgrade to HTTP/2.0.
  • 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.
  • HTTP/2.0 without TLS is however a separate protocol (h2c) and some implementations miss support for plaintext HTTP/2.0 (intentionally, to get rid of plaintext HTTP).
  • But most backend stacks run on plaintext HTTP simply because there’s little point of running full-blown TLS between localhost and localhost.
  • So, migration from HTTP/1.1 to HTTP/2.0 in backend isn’t just matter of switching protocols - I’ve been there.

https://portswigger.net/blog/http-1-1-must-die-what-this-means-for-appsec-leadership

PortSwigger Blog · HTTP/1.1 Must Die: What This Means for AppSec LeadershipLearn the implications of and how to defend your organization against HTTP/1.1 request smuggling.