Repository navigation
Explain how HTTP header fields integrate with URL patterns - #230
Conversation
Per discussion on whatwg#182 some text explaining this would be useful.
|
@domenic @annevk does this address the concern in #182 (comment)? |
Co-authored-by: Domenic Denicola <d@domenic.me>
|
|
||
| <h3 id=other-specs-http>Integrating with HTTP header fields</h3> | ||
|
|
||
| HTTP headers which include URL patterns should accept a string in the constructor string syntax, likely as part of a structured field [[RFC8941]]. |
There was a problem hiding this comment.
What is "constructor string syntax"? Is this talking about the URLPattern constructor which it below says should not be relied upon?
There was a problem hiding this comment.
It refers to the syntax that is accepted when a single string is passed to the constructor (i.e., is accepted by the constructor string parser), as opposed to the pattern syntax for a single component.
It could be renamed something else, but this is how the spec currently refers to that syntax.
There was a problem hiding this comment.
I think if the syntax is defined somewhere and you can xref it that seems reasonable. Otherwise it seems rather opaque to me.
There was a problem hiding this comment.
Added links to the constructor string parsing section.
Per discussion on #182 some text explaining this would be useful.
This mostly consists of advice since the useful algorithms are already exposed.
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff