#contentlength
Live, measured metrics for the hashtag #contentlength from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #contentlength
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 09:08 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 09:08 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:08 UTCEverything below is measured over the latest 3 public posts (spanning ~21626 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.3
Top of the latest posts
So yes, it turns out that though our communication partner pretends to accept HTTP/2, their API server adheres to HTTP/1.1 standards. And with HTTP/1.1, the #Java11 #HttpClient will send a #ContentLength header even if the payload is 0 byte
It looks like #Java11 decided to completely omit the #contentLength header of an #HttpPost request if the content length equals 0 (zero). That's possible with HTTP/2, but not with HTTP/1.0 or 1.1. The #RESTAPI server we talk to requires a c
Yesterday was the first time in years a remote #REST #API server required me to send the #ContentLength #requestHeader. The #HTTP component I was using, #HttpURLConnection by Sun, outright refused to set it. I looked up the HTTP RFC: yes, i
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/contentlength