You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sync service uses custom headers starting with x-, however, this convention has been deprecated since 2012 and is actually advised against doing that (cf. https://datatracker.ietf.org/doc/html/rfc6648#page-4).
Recommendations for Creators of New Parameters
Creators of new parameters to be used in the context of application
protocols:
SHOULD assume that all parameters they create might become standardized, public, commonly deployed, or usable across multiple implementations.
SHOULD employ meaningful parameter names that they have reason to believe are currently unused.
SHOULD NOT prefix their parameter names with "X-" or similar constructs.
Note: If the relevant parameter name space has conventions about associating parameter names with those who create them, a parameter name could incorporate the organization's name or primary domain name (see Appendix B for examples).
We already follow their advise of incorporating our organisation name, so we should rename headers like x-electric-shape-id to electric-shape-id.
The text was updated successfully, but these errors were encountered:
This PR removes the x- prefix from Electric's custom headers, as
essentially the x- prefix has been deprecated for a while. **This is a
breaking change** as it changes the names of the headers. Fixes#1737.
The sync service uses custom headers starting with
x-
, however, this convention has been deprecated since 2012 and is actually advised against doing that (cf. https://datatracker.ietf.org/doc/html/rfc6648#page-4).We already follow their advise of incorporating our organisation name, so we should rename headers like
x-electric-shape-id
toelectric-shape-id
.The text was updated successfully, but these errors were encountered: