Skip to content

Commit 4b5603c

Browse files
authored
Structured Fields is RFC 8941 now! (#10)
1 parent d4233da commit 4b5603c

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,11 @@ Provides parsing and serialization facilities for structured header fields, as w
66

77
## About Structured Header Fields
88

9-
HTTP Structured Header fields are [a draft specification](https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-19) being worked on by the IETF. They provide a set of data types and algorithms for handling HTTP header field values in a consistent way, allowing a single parser and serializer to handle a wide range of header field values.
9+
HTTP Structured Header fields are a HTTP extension recorded in [RFC 8941](https://www.rfc-editor.org/rfc/rfc8941.html) . They provide a set of data types and algorithms for handling HTTP header field values in a consistent way, allowing a single parser and serializer to handle a wide range of header field values.
1010

1111
## Swift HTTP Structured Header Fields
1212

13-
This package provides a parser and serializer that match draft 19 of the working group's draft specification. They are entirely complete, able to handle all valid HTTP structured header fields. This package also provides `Encoder` and `Decoder` objects for working with Codable in Swift. This allows rapid prototyping and experimentation with HTTP structured header fields, as well as interaction with the wider Swift Codable community.
13+
This package provides a parser and serializer that implement RFC 8941. They are entirely complete, able to handle all valid HTTP structured header fields. This package also provides `Encoder` and `Decoder` objects for working with Codable in Swift. This allows rapid prototyping and experimentation with HTTP structured header fields, as well as interaction with the wider Swift Codable community.
1414

1515
This package provides two top-level modules: `StructuredHeaders` and `CodableStructuredHeaders`.
1616

@@ -24,7 +24,7 @@ In most cases users should prefer to use `CodableStructuredHeaders` unless they
2424

2525
## Working with Structured Header Fields
2626

27-
`swift-http-structured-headers` has a simply, easy-to-use high-level API for working with structured header fields. To begin with, let's consider the [HTTP Client Hints draft specification](https://tools.ietf.org/html/draft-ietf-httpbis-client-hints-15). This defines the following new header field:
27+
`swift-http-structured-headers` has a simply, easy-to-use high-level API for working with structured header fields. To begin with, let's consider the [HTTP Client Hints specification](https://www.rfc-editor.org/rfc/rfc8942.html). This defines the following new header field:
2828

2929
> The Accept-CH response header field indicates server support for the hints indicated in its value. Servers wishing to receive user agent information through Client Hints SHOULD add Accept-CH response header to their responses as early as possible.
3030
>

Sources/StructuredHeaders/FieldParser.swift

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ extension StructuredFieldParser {
3636

3737
/// Parse the HTTP structured field as a list.
3838
///
39-
/// This is a straightforward implementation of the parser in the draft spec.
39+
/// This is a straightforward implementation of the parser in the spec.
4040
///
4141
/// - throws: If the field could not be parsed.
4242
/// - returns: An array of items or inner lists.

0 commit comments

Comments
 (0)