Tag: Symfony
-
What a service worker must never cache
Caching the wrong response does not produce an error. It produces a wrong answer, delivered confidently, for as long as the cache lives.
-
Making a Symfony application installable, without a framework for it
A progressive web app needs a manifest, a service worker and a few icons. Most of the work is deciding what should happen offline.
-
Web push notifications from PHP, without a service in between
A push subscription is a URL, a public key and a secret. Everything else is your server talking directly to the browser vendor.
-
Passkeys: what actually changes for your PHP application
Passkeys are Webauthn credentials that sync. That single difference changes your data model, your recovery flow and what you can promise your users.
-
The Webauthn registration ceremony, step by step
What actually happens between clicking « add a security key » and having a credential you can trust. Six steps, and the three where implementations go wrong.
-
Bridging two ecosystems rather than forking one
LexikJWTAuthenticationBundle handles authentication. JWT-Framework handles JOSE. A bridge is a hundred lines; a fork would have been a second project to maintain.
-
JWT-Framework v1.1.0
Almost four months after the first stable release of JWT-Framework, a new version is about to ship. It is a minor release, but it brings a number of changes. Here are the main ones.