Fixing the URL params performance penalty

Tales of two pages… What's the difference between these two pages?: https://www.example.com/ https://www.example.com/?utm_source=email I mean they've got different URLs, but many of us would probably guess that that utm_source URL query parameters (or "URL params" or "search params" as it's

Web Performance Calendar

CORS Explained: Stop Struggling With Cross-Origin Errors, by (not on Mastodon or Bluesky):

https://archive.fo/5rWqj

#security #cors #httpheaders #http

RFC 8594: The Sunset HTTP Header Field

This specification defines the Sunset HTTP response header field, which indicates that a URI is likely to become unresponsive at a specified point in the future. It also defines a sunset link relation type that allows linking to resources providing information about an upcoming resource or service sunset.

IETF Datatracker
Chrome 140 introduces HTTP cookie prefix to combat client-side security threats: Chrome 140 beta introduces __Http and __HostHttp cookie prefixes on August 6, 2025, enabling servers to distinguish server-set from client-set cookies. https://ppc.land/chrome-140-introduces-http-cookie-prefix-to-combat-client-side-security-threats/ #Chrome140 #HTTPHeaders #WebSecurity #Cookies #ClientSideSecurity
Chrome 140 introduces HTTP cookie prefix to combat client-side security threats

Chrome 140 beta introduces __Http and __HostHttp cookie prefixes on August 6, 2025, enabling servers to distinguish server-set from client-set cookies.

PPC Land
🧙‍♂️ Ah, yes, because nothing screams cutting-edge tech quite like slapping a fictional telegraph homage from a fantasy series onto modern HTTP headers. 🤦‍♂️ Let's all pause to admire the nerdy zealotry that ensures the name of a character floats eternally through the internet... because nothing could be more crucial. 🙄
https://xclacksoverhead.org/home/about #cuttingEdgeTech #nerdyHumor #HTTPHeaders #fantasyTech #telegraphTribute #HackerNews #ngated
XClacksOverhead.org

Information on the X-Clacks-Overhead transmission header.

X-Clacks-Overhead
Progressive Dehancement

The one where I try my best to fight spam and not surrender

dbushell.com
I guess some request headers are more trustworthy than others.

There's a subset of request headers that can't be modified by a spec-compliant user agent. Let's explore why they're useful for determining how and for what purpose a request was triggered.

Alex MacArthur
Why Do We Have a Cache-Control Request Header? – CSS Wizardry

Learn how the Cache-Control request header works, how browsers handle refresh and hard refresh caching, and when developers should use it for realtime data and offline-first applications.

Although frequently misunderstood, the HTTP Cache-Control header is crucial because it specifies caching mechanisms within requests and responses.  In its typical format, it reveals details as to how resources are stored, the location of the resource and the maximum age before expiring…

In our latest blog post, Kieran Larking highlights that the No-cache directive does not prevent caching and looks at typical caching behaviour directives and how to correctly use these directives to balance performance and security: https://www.pentestpartners.com/security-blog/take-control-of-cache-control-and-local-caching/

#Caching #CacheControl #WebPerformance #WebSecurity #HTTPHeaders #Cybersecurity #DeveloperGuide #HTTP

Take control of Cache-Control and local caching | Pen Test Partners

TL;DR Caching speeds up website content delivery What caching directives are and how to use them The No-cache directive does not prevent caching The No-store directive prevents caching Introduction The HTTP Cache-Control header is sometimes misunderstood. It's important because it is used to specify caching mechanisms within requests and responses. In its typical format, it

#Development #Techniques
Avoid hotlinking images with CORP · How to stop other websites from serving your images https://ilo.im/1613tb

_____
#Images #Security #HTTP #HttpHeaders #CORP #Browser #Hosting #WebDev #Frontend #Backend

Avoid hotlinking images with Cross-Origin-Resource-Policy

An image on your site can be directly included in other sites. You end up with the costs of hosting and serving the image, while the other sites gain the benefits of showing your nice image on their page. With the response header Cross-Origin-Resource-Policy it is possible to inform the browser that images should only be usable by the same site or origin as the image, thus making hotlinking impossible.

Sjoerd Langkemper