-
Notifications
You must be signed in to change notification settings - Fork 115
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rename "trailing" to "trailer" headers
- Loading branch information
1 parent
c9b9e6a
commit 2ce7593
Showing
11 changed files
with
149 additions
and
147 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -115,7 +115,7 @@ | |
* Fix a small bug with double "wrapping" of some `Mint.TransportError`s. | ||
* Prevent unnecessary buffer allocations in the connections (less memory waste!). | ||
* Add support for chunked transfer-encoding in HTTP/1 requests when you don't use `content-encoding`/`transfer-encoding` yourself. | ||
* Add support for trailing headers in HTTP/* requests through `stream_request_body/3`. | ||
* Add support for trailer headers in HTTP/* requests through `stream_request_body/3`. | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
whatyouhide
Author
Contributor
|
||
* Add a page about decompressing responses in the guides. | ||
|
||
## v0.3.0 | ||
|
@@ -136,7 +136,7 @@ | |
|
||
* Add `Mint.HTTP.controlling_process/2`, `Mint.HTTP1.controlling_process/2`, and `Mint.HTTP2.controlling_process/2` to change the controlling process of a connection. | ||
|
||
* Support trailing response headers in HTTP/2 connections. | ||
* Support trailer response headers in HTTP/2 connections. | ||
|
||
## v0.2.1 | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
trailer header feels like a misnomer though. should be trailer fields or trailers just like we have header fields or headers. But it might be a pragmatic choice to use this particular naming given we send them as :headers as well as users might not be aware of trailers (but then should they be using Mint? 🤔 😉). So yeah I think this is fine. thanks for making this change!