-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TSV-ART review from Magnus Westerlund #131
Merged
Merged
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
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 |
---|---|---|
|
@@ -184,8 +184,37 @@ | |
<t> | ||
Examples in this document use the <xref target="RFC7230">HTTP/1.1 | ||
message format</xref>. Many of the exchanges can be completed using | ||
HTTP/1.1. Where HTTP/2 is necessary, the more verbose frame format | ||
from <xref target="RFC7540"/> is used. | ||
HTTP/1.1: | ||
|
||
<list style="symbols"> | ||
<t> | ||
<xref target="message_subscription">Subscribing for Push Messages</xref> | ||
</t> | ||
<t> | ||
<xref target="send">Requesting Push Message Delivery</xref> | ||
</t> | ||
<t> | ||
<xref target="replace">Replacing Push Messages</xref> | ||
</t> | ||
<t> | ||
<xref target="acknowledge_message">Acknowledging Push Messages</xref> | ||
</t> | ||
</list> | ||
|
||
Where HTTP/2 server push is required, the more verbose frame format | ||
from <xref target="RFC7540"/> is used: | ||
|
||
<list style="symbols"> | ||
<t> | ||
<xref target="monitor-subscription">Receiving Push Messages for a Subscription</xref> | ||
</t> | ||
<t> | ||
<xref target="monitor-set">Receiving Push Messages for a Subscription Set</xref> | ||
</t> | ||
<t> | ||
<xref target="receive_receipt">Receiving Push Message Receipts</xref> | ||
</t> | ||
</list> | ||
</t> | ||
<t> | ||
Examples do not include specific methods for push message encryption | ||
|
@@ -1075,13 +1104,13 @@ HEADERS [stream 82] +END_STREAM | |
in response to requests that include an entity body that is too large. | ||
Push services MUST NOT return a 413 status code in responses to an entity | ||
body that is 4096 bytes or less in size. | ||
</t> | ||
</t> | ||
<t> | ||
To limit the number of stored push messages, the push service MAY respond with a shorter | ||
Time-To-Live than proposed by the application server in its request for push message delivery | ||
(<xref target="ttl"/>). Once a message has been accepted, the push service MAY later expire | ||
the message prior to its advertised Time-To-Live. If the application server requested a | ||
delivery receipt, the push service MUST return a failure response (<xref target="acknowledge_message"/>). | ||
delivery receipt, the push service MUST return a failure response (s<xref target="acknowledge_message"/>). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is that "s" in the parenthesis spurious? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Doh. Yes. I was editing out a see and managed to miss the s. Thanks. |
||
</t> | ||
</section> | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some IETF curmudgeons will get their panties in a twist over "required", since "REQUIRED" is an RFC 2119 keyword. I tend to avoid it to avoid the pedants.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sound advice. Updated.