Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
cf3fa6ee
Commit
cf3fa6ee
authored
Sep 13, 2021
by
Poul-Henning Kamp
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add text about RFC8941 Structured Fields
parent
24b901cc
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
32 additions
and
3 deletions
+32
-3
changes-trunk.rst
doc/sphinx/whats-new/changes-trunk.rst
+32
-3
No files found.
doc/sphinx/whats-new/changes-trunk.rst
View file @
cf3fa6ee
...
...
@@ -31,10 +31,39 @@ regular expressions are used, like VCL, ban expressions, VSL queries etc.
There were some parameters changes, see the upgrade notes for more details.
Structured Fields number
s
=========================
RFC8941 - Structured Field
s
=========================
==
TODO (probably deserves its own section too)
It will come as no surprise to VCL writers that HTTP headers use what can
charitably be described as "heterogenous syntax".
In 2016, on the train back from the HTTP Workshop in Stockholm, and
in response to proposals to allow JSON in HTTP headers, I started an effort
which culminated with the publication of `RFC 8941 Structured Fields`_.
The syntax in Structured Fields is distilled from current standardized headers,
which means that the vast majority of existing HTTP headers are already
covered.
There are unfortunate exceptions, most notably the Cookie headers.
Starting with this release, we are gently migrating VCL towards the
Structured Field semantics.
The first change is that it is now possible to include BLOBs in VCL,
by using the RFC 8941 syntax of::
':' + <base64> + ':'
The second and likely more significant change is numbers in VCL
now conform to RFC8941 as well: Up to 15 digits and at most 3
decimal places.
(These restrictions were chosen after much careful deliberation, to
ensure that no overflows would occur, even when HTTP headers are
processed in languages where numbers are represented by IEEE-754
64 binary floating point variables,)
.. _RFC 8941 Structured Fields: https://www.rfc-editor.org/rfc/rfc8941.html
varnishd
========
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment