@@ -30,16 +30,16 @@ The syntax for the `WAC-Allow` header, using the ABNF syntax defined in
30
30
Section 1.2 of [[!RFC7231]] , is:
31
31
32
32
```
33
- wac-allow = "WAC-Allow" ":" OWS #access-param OWS
34
- access-param = permission-group OWS "=" OWS quoted- access-modes
35
- permission-group = 1*ALPHA
36
- quoted- access-modes = DQUOTE OWS *1(access-mode *(RWS access-mode)) OWS DQUOTE
37
- access-mode = "read" / "write" / "append" / "control"
33
+ wac-allow = "WAC-Allow" ":" OWS #access-param OWS
34
+ access-param = permission-group OWS "=" OWS access-modes
35
+ permission-group = 1*ALPHA
36
+ access-modes = *1DQUOTE OWS *1(access-mode *(RWS access-mode)) OWS *1DQUOTE
37
+ access-mode = "read" / "write" / "append" / "control"
38
38
```
39
39
40
40
The `WAC-Allow` HTTP header's field-value is a comma-separated list of
41
41
`access-param`s. `access-param` is a whitespace-separated list of `access
42
- mode`s granted to a `permission-group`.
42
+ modes` granted to a `permission-group`.
43
43
44
44
This specification defines the following `permission-group`s:
45
45
@@ -62,6 +62,10 @@ handling. When the received message fails to match an allowed pattern, finds
62
62
unrecognised access parameters or access modes, clients MUST ignore the
63
63
received `WAC-Allow` header-field.
64
64
65
+ The quoted and unquoted values for `access-modes` are equivalent. Servers are
66
+ recommended to use quoted values in the response. Clients' are recommended to
67
+ be able to parse both quoted and unquoted values.
68
+
65
69
[[Source] (https://github.com/solid/specification/issues/171)]
66
70
[[Source] (https://github.com/solid/specification/issues/170)]
67
71
[[Source] (https://github.com/solid/specification/issues/181)]
0 commit comments