Hi Sling Developers,
As modern HTTP header fields increasingly rely on RFC 9651 (which
obsoleted RFC 8941), my Java implementation
(https://github.com/reschke/structured-fields) is looking for a cozy
home under the Apache umbrella.
I propose creating a standalone org.apache.sling.http.structuredfields
bundle wrapping this zero-dependency library.
Why this makes sense:
Modularity: Keeps core Sling lean while letting interested bundles opt-in.
Sanity: Replaces error-prone string splitting with a robust,
spec-compliant service.
I’m happy to get the ball rolling in the Sling Whiteboard. Does the
community think this is a good spot for it?
Best regards,
Julian Reschke
PS: see https://datatracker.ietf.org/doc/rfc8941/referencedby/ and
https://datatracker.ietf.org/doc/rfc9651/referencedby/ for specs using
this syntax.
