draft-ietf-httpbis-origin-frame-04.txt   draft-ietf-httpbis-origin-frame-latest.txt 
HTTP Working Group M. Nottingham HTTP Working Group M. Nottingham
Internet-Draft Internet-Draft
Intended status: Standards Track E. Nygren Intended status: Standards Track E. Nygren
Expires: vergleich dating seiten deutschland February 24, 2018 Akamai Expires: we chat software for nokia 2690 May 22, 2018 Akamai
wechat application for nokia 2690 August 23, 2017 java lan chat application source code November 18, 2017
The ORIGIN HTTP/2 Frame The ORIGIN HTTP/2 Frame
baixar jogos de futebol para celular samsung chat 222 draft-ietf-httpbis-origin-frame-04 java chat server source code draft-ietf-httpbis-origin-frame-latest
Abstract Abstract
This document specifies the ORIGIN frame for HTTP/2, to indicate what This document specifies the ORIGIN frame for HTTP/2, to indicate what
origins are available on a given connection. origins are available on a given connection.
Note to Readers Note to Readers
Discussion of this draft takes place on the HTTP working group Discussion of this draft takes place on the HTTP working group
mailing list ([email protected]), which is archived at mailing list ([email protected]), which is archived at
skipping to change at page 1, line 42java client server chat application source code ¶ skipping to change at page 1, line 42chat cu fete si baieti web ¶
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on code source java chat client serveur February 24, 2018. This Internet-Draft will expire on descargar wechat gratis para movil May 22, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 21descargar facebook chat gratis para móvil ¶ skipping to change at page 2, line 21descargar chats gratis para movil ¶
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3 1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3
2. The ORIGIN HTTP/2 Frame . . . . . . . . . . . . . . . . . . . 3 2. The ORIGIN HTTP/2 Frame . . . . . . . . . . . . . . . . . . . 3
2.1. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Processing ORIGIN Frames . . . . . . . . . . . . . . . . descargar tuenti chat gratis para movil 3 2.2. Processing ORIGIN Frames . . . . . . . . . . . . . . . . whatsapp dlya nokia e52 skachat 4
2.3. The Origin Set . . . . . . . . . . . . . . . . . . . . . 4 2.3. The Origin Set . . . . . . . . . . . . . . . . . . . . . 4
2.4. Authority, Push and Coalescing with ORIGIN . . . . . . . 5 2.4. Authority, Push and Coalescing with ORIGIN . . . . . . . 5
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . apps wechat java jar 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . install whatsapp for samsung chat 222 7
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Normative References . . . . . . . . . . . . . . . . . . 7 5.1. Normative References . . . . . . . . . . . . . . . . . . 7
5.2. Informative References . . . . . . . . . . . . . . . . . 8 5.2. Informative References . . . . . . . . . . . . . . . . . 8
5.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . sims 3 spielen kostenlos ohne cd 8 5.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . facebook chat java phonekey 9
Appendix A. Non-Normative Processing Algorithm . . . . . . . . . facebook chat java mobile application 8 Appendix A. Non-Normative Processing Algorithm . . . . . . . . . facebook chat java mobile software 9
Appendix B. Operational Considerations for Servers . . . . . . . 9 Appendix B. Operational Considerations for Servers . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
HTTP/2 [RFC7540] allows clients to coalesce different origins HTTP/2 [RFC7540] allows clients to coalesce different origins
[RFC6454] onto the same connection when certain conditions are met. [RFC6454] onto the same connection when certain conditions are met.
However, in certain cases, a connection is not usable for a coalesced However, in certain cases, a connection is not usable for a coalesced
origin, so the 421 (Misdirected Request) status code ([RFC7540], origin, so the 421 (Misdirected Request) status code ([RFC7540],
Section 9.1.2) was defined. Section 9.1.2) was defined.
skipping to change at page 3, line 10facebook chat java mobile app ¶ skipping to change at page 3, line 10java apps kostenlos herunterladen ¶
Additionally, experience has shown that HTTP/2's requirement to Additionally, experience has shown that HTTP/2's requirement to
establish server authority using both DNS and the server's establish server authority using both DNS and the server's
certificate is onerous. This specification relaxes the requirement certificate is onerous. This specification relaxes the requirement
to check DNS when the ORIGIN frame is in use. Doing so has to check DNS when the ORIGIN frame is in use. Doing so has
additional benefits, such as removing the latency associated with additional benefits, such as removing the latency associated with
some DNS lookups. some DNS lookups.
1.1. Notational Conventions 1.1. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", intranet chatting project in java with source code "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in lan chat and file sharing java project source code [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in lan chat messenger source code in java BCP
lan voice chat java source code 14 [RFC2119] [RFC8174] when, and only when, they appear in all
sims 3 kostenlos objekte runterladen capitals, as shown here.
2. The ORIGIN HTTP/2 Frame 2. The ORIGIN HTTP/2 Frame
The ORIGIN HTTP/2 frame ([RFC7540], Section 4) allows a server to The ORIGIN HTTP/2 frame ([RFC7540], Section 4) allows a server to
indicate what origin(s) [RFC6454] the server would like the client to indicate what origin(s) [RFC6454] the server would like the client to
consider as members of the Origin Set (Section 2.3) for the consider as members of the Origin Set (Section 2.3) for the
connection it occurs within. connection it occurs within.
2.1. Syntax 2.1. Syntax
The ORIGIN frame type is 0xc (decimal 12), and contains zero chat cu web fete si baitei to many The ORIGIN frame type is 0xc (decimal 12), and contains zero skachat besplatno whatsapp dlya nokia e51 or more
module live chat joomla 2.5 Origin-Entry. zopim live chat joomla 2.5 instances of the Origin-Entry field.
+-------------------------------+-------------------------------+ +-------------------------------+-------------------------------+
| Origin-Entry (*) ... | Origin-Entry (*) ...
+-------------------------------+-------------------------------+ +-------------------------------+-------------------------------+
An Origin-Entry is a length-delimited string: An Origin-Entry is a length-delimited string:
+-------------------------------+-------------------------------+ +-------------------------------+-------------------------------+
| Origin-Len (16) | ASCII-Origin? ... | Origin-Len (16) | ASCII-Origin? ...
+-------------------------------+-------------------------------+ +-------------------------------+-------------------------------+
skipping to change at page 4, line 18live support chat joomla 2.5 ¶ skipping to change at page 4, line 23skachat besplatno whatsapp dlya nokia e52 ¶
The origin frame MUST be sent on stream 0; an ORIGIN frame on any The origin frame MUST be sent on stream 0; an ORIGIN frame on any
other stream is invalid and MUST be ignored. other stream is invalid and MUST be ignored.
Likewise, the ORIGIN frame is only valid on connections with the "h2" Likewise, the ORIGIN frame is only valid on connections with the "h2"
protocol identifier, or when specifically nominated by the protocol's protocol identifier, or when specifically nominated by the protocol's
definition; it MUST be ignored when received on a connection with the definition; it MUST be ignored when received on a connection with the
"h2c" protocol identifier. "h2c" protocol identifier.
This specification does not define any flags for the ORIGIN frame, This specification does not define any flags for the ORIGIN frame,
but future updates might use them to change its semantics. The first but future updates wechat app for nokia 2690 to this specification (through IETF consensus)
four flags (0x1, 0x2, 0x4 and 0x8) are reserved for web based skype chat backwards- might use them to change its semantics. The first four flags (0x1,
skachat whatsapp nokia e51 incompatible changes, and therefore when any of them are set, the 0x2, 0x4 and 0x8) are reserved for chat server source code in c backwards-incompatible changes,
ORIGIN frame containing them MUST be ignored by clients conforming to and therefore when any of them are set, the ORIGIN frame containing
this specification, unless the flag's semantics are understood. The them MUST be ignored by clients conforming to this specification,
remaining flags are reserved for backwards-compatible changes, and do unless the flag's semantics are understood. The remaining flags are
not affect processing by clients conformant to this specification. reserved for backwards-compatible changes, and do not affect
processing by clients conformant to this specification.
The ORIGIN frame describes a property of the connection, and The ORIGIN frame describes a property of the connection, and
therefore is processed hop-by-hop. An intermediary MUST NOT forward therefore is processed hop-by-hop. An intermediary MUST NOT forward
ORIGIN frames. Clients configured to use a proxy MUST ignore any ORIGIN frames. Clients configured to use a proxy MUST ignore any
ORIGIN frames received from it. ORIGIN frames received from it.
Each ASCII-Origin field in the frame's payload MUST be parsed as an Each ASCII-Origin field in the frame's payload MUST be parsed as an
ASCII serialisation of an origin ([RFC6454], Section 6.2). If ASCII serialisation of an origin ([RFC6454], Section 6.2). If
parsing fails, the field MUST be ignored. parsing fails, the field MUST be ignored.
skipping to change at page 4, line 50chat server source code ¶ skipping to change at page 5, line 7whatsapp samsung chat 335 descargar gratis ¶
The set of origins (as per [RFC6454]) that a given connection might The set of origins (as per [RFC6454]) that a given connection might
be used for is known in this specification as the Origin Set. be used for is known in this specification as the Origin Set.
By default, the Origin Set for a connection is uninitialised. When By default, the Origin Set for a connection is uninitialised. When
an ORIGIN frame is first received and successfully processed by a an ORIGIN frame is first received and successfully processed by a
client, the connection's Origin Set is defined to contain an initial client, the connection's Origin Set is defined to contain an initial
origin. The initial origin is composed from: origin. The initial origin is composed from:
o Scheme: "https" o Scheme: "https"
o Host: the value sent in Server Name Indication (SNI, [RFC6066] o Host: the value sent in Server Name Indication (SNI, [RFC6066]whatsapp samsung chat 335 java gratis ,
Section 3), converted to lower case Section 3), converted to lower case
o Port: the remote port of the connection (i.e., the server's port) o Port: the remote port of the connection (i.e., the server's port)
The contents of that ORIGIN frame (and subsequent ones) allows the The contents of that ORIGIN frame (and subsequent ones) allows the
server to incrementally add new origins to the Origin Set, as server to incrementally add new origins to the Origin Set, as
described in Section 2.2. described in Section 2.2.
The Origin Set is also affected by the 421 (Misdirected Request) The Origin Set is also affected by the 421 (Misdirected Request)
response status code, defined in [RFC7540] Section 9.1.2. Upon response status code, defined in [RFC7540]facebook chat java mobile apps , Section 9.1.2. Upon
receipt of a response with this status code, implementing clients receipt of a response with this status code, implementing clients
MUST create the ASCII serialisation of the corresponding request's MUST create the ASCII serialisation of the corresponding request's
origin (as per [RFC6454], Section 6.2) and remove it from the origin (as per [RFC6454], Section 6.2) and remove it from the
connection's Origin Set, if present. connection's Origin Set, if present.
Note: When sending an ORIGIN frame to a connection that is Note: When sending an ORIGIN frame to a connection that is
initialised as an Alternative Service [RFC7838], the initial initialised as an Alternative Service [RFC7838], the initial
origin set java spiele kostenlos runterladen Section 2.3 will contain an origin with the appropriate origin set java spiele kostenlos herunterladen (Section 2.3) will contain an origin with the
scheme and hostname (since Alternative Services specifies that the appropriate scheme and hostname (since Alternative Services
origin's hostname be sent in SNI). However, it is possible that specifies that the origin's hostname be sent in SNI). However, it
the port will be different than that of the intended origin, since is possible that the port will be different than that of the
the initial origin set is calculated using the actual port in use, intended origin, since the initial origin set is calculated using
which can be different for the alternative service. In this case, the actual port in use, which can be different for the alternative
the intended origin needs to be sent in the ORIGIN frame service. In this case, the intended origin needs to be sent in
explicitly. the ORIGIN frame explicitly.
For example, a client making requests for "https://example.com" is For example, a client making requests for "https://example.com" is
directed to an alternative service at ("h2", "x.example.net", directed to an alternative service at ("h2", "x.example.net",
"8443"). If this alternative service sends an ORIGIN frame, the "8443"). If this alternative service sends an ORIGIN frame, the
initial origin will be "https://example.com:8443". The client initial origin will be "https://example.com:8443". The client
will not be able to use the alternative service to make requests will not be able to use the alternative service to make requests
for "https://example.com" unless that origin is explicitly for "https://example.com" unless that origin is explicitly
included in the ORIGIN frame. included in the ORIGIN frame.
2.4. Authority, Push and Coalescing with ORIGIN 2.4. Authority, Push and Coalescing with ORIGIN
sims 3 kostenlos möbel runterladen [RFC7540], Section 10.1 uses both DNS and the presented TLS sims 3 häuser kostenlos runterladen Section 10.1 of [RFC7540] uses both DNS and the presented TLS
certificate to establish the origin server(s) that a connection is certificate to establish the origin server(s) that a connection is
authoritative for, just as HTTP/1.1 does in [RFC7230]. authoritative for, just as HTTP/1.1 does in [RFC7230].
Furthermore, sims 3 kostenlos kleidung runterladen [RFC7540] Section 9.1.1 explicitly allows a connection Furthermore, Section 9.1.1 sims 3 kostenlos kleidung herunterladen of [RFC7540] explicitly allows a
to be used for more than one origin server, if it is authoritative. connection to be used for more than one origin server, if it is
This affects what sims 3 möbel kostenlos herunterladen requests can be sims 3 häuser kostenlos herunterladen sent on the connection, both code source application client serveur chat en java in authoritative. This affects what descargar wechat gratis para movil lg responses can be sims 3 objekte kostenlos considered
c# chat server source code HEADERS frame by the client and chat application source code in c# as PUSH_PROMISE frames from the chat messenger source code in c# authoritative, both chat source code in c# for direct responses to requests and chat client server source code for server
server chatbot c++ source code ([RFC7540], Section 8.2.2). chat room source code in c# push (see [RFC7540], Section 8.2.2). client server chat source code in c Indirectly, it also affects
chat client server java source code what requests will be sent on a connection, since clients will
chat server source code in java generally only send requests on connections that they believe to be
android chat client server source code authoritative for the origin in question.
Once an Origin Set has been initialised for a connection, clients Once an Origin Set has been initialised for a connection, clients
that implement this specification use it to help determine what the that implement this specification use it to help determine what the
connection is authoritative for. Specifically, such clients MUST NOT connection is authoritative for. Specifically, such clients MUST NOT
consider a connection to be authoritative for an origin not present consider a connection to be authoritative for an origin not present
in the Origin Set, and SHOULD use the connection for all requests to in the Origin Set, and SHOULD use the connection for all requests to
origins in the Origin Set for which the connection is authoritative, origins in the Origin Set for which the connection is authoritative,
unless there are operational reasons for opening a new connection. unless there are operational reasons for opening a new connection.
Note that for a connection to be considered authoritative for a given Note that for a connection to be considered authoritative for a given
origin, the client is still required to obtain a certificate that origin, the client is still required to obtain a certificate that
passes suitable checks; see descargar whatsapp para samsung chat 335 gratis argim [RFC7540] Section 9.1.1 for more passes suitable checks; see descargar whatsapp para samsung chat 335 gratis java Section 9.1.1 of [RFC7540] for more
information. This includes verifying that the host matches a information. This includes verifying that the host matches a
"dNSName" value from the certificate "subjectAltName" field (using "dNSName" value from the certificate "subjectAltName" field (using
the samsung chat 335 whatsapp descargar español gratis wildcard rules defined in [RFC2818]; see also whatsapp para samsung chat 335 descargar gratis [RFC5280] the rules defined in [RFC2818]; see also whatsapp para samsung chat 335 descargar gratis en español [RFC5280], Section 4.2.1.6).
Section 4.2.1.6).
Additionally, clients MAY avoid consulting DNS to establish the Additionally, clients MAY avoid consulting DNS to establish the
connection's authority for new requests; however, those that do so connection's authority for new requests; however, those that do so
face new risks, as explained in Section 4 face new risks, as explained in Section 4descargar whatsapp para samsung chat 335 gratis sin android .
Because ORIGIN can change the set of origins a connection is used for Because ORIGIN can change the set of origins a connection is used for
over time, it is possible that a client might have more than one over time, it is possible that a client might have more than one
viable connection to an origin open at any time. When this occurs, viable connection to an origin open at any time. When this occurs,
clients SHOULD sims 3 objekte kostenlos herunterladen not emit new requests on any connection whose Origin clients SHOULD descargar whatsapp para samsung chat 335 java gratis en español NOT emit new requests on any connection whose Origin
Set is a proper subset of another connection's Origin Set, and SHOULD Set is a proper subset of another connection's Origin Set, and SHOULD
close it once all outstanding requests are satisfied. close it once all outstanding requests are satisfied.
The Origin Set is unaffected by any alternative services [RFC7838] The Origin Set is unaffected by any alternative services [RFC7838]
advertisements made by the server. Advertising an alternative advertisements made by the server. Advertising an alternative
service does not affect whether a server is authoritative. service does not affect whether a server is authoritative.
3. IANA Considerations 3. IANA Considerations
This specification adds an entry to the "HTTP/2 Frame Type" registry. This specification adds an entry to the "HTTP/2 Frame Type" registry.
skipping to change at page 7, line 8whatsapp para samsung chat 335 java español gratis ¶ skipping to change at page 7, line 19whatsapp para samsung chat 335 java gratis ¶
mitigations. mitigations.
Relaxing the requirement to consult DNS when determining authority Relaxing the requirement to consult DNS when determining authority
for an origin means that an attacker who possesses a valid for an origin means that an attacker who possesses a valid
certificate no longer needs to be on-path to redirect traffic to certificate no longer needs to be on-path to redirect traffic to
them; instead of modifying DNS, they need only convince the user to them; instead of modifying DNS, they need only convince the user to
visit another Web site in order to coalesce connections to the target visit another Web site in order to coalesce connections to the target
onto their existing connection. onto their existing connection.
As a result, clients opting not to consult DNS ought to employ some As a result, clients opting not to consult DNS ought to employ some
alternative means to descargar whatsapp para samsung chat 335 java gratis increase confidence that the certificate is alternative means to install whatsapp on my samsung chat 222 establish a high degree of confidence that the
whatsapp for samsung chat 322 legitimate. Examples of mechanisms that can give additional certificate is legitimate. For c# chat source code example, clients might skip
live chat source code in asp net c# confidence in a certificate include checking for a Signed Certificate consulting DNS only if they receive proof of inclusion in a
chat program source code c# Timestamp [RFC6929] and performing certificate revocation checks. Certificate Transparency log [RFC6929] or they have a recent OCSP
c# chatbot source code response [RFC6960] (possibly using the "status_request" TLS extension
lan chat source code c# Clients opting not to consult DNS ought to do so only if they have a [RFC6066]) showing that the certificate was not revoked.
high degree of confidence that the certificate is legitimate. For
voice chat source code c# instance, clients might skip consulting DNS only if they receive
proof of inclusion in a Certificate Transparency log [RFC6929] or
they have a recent OCSP response [RFC6960] (possibly using the
"status_request" TLS extension [RFC6066]) showing that the
certificate was not revoked.
The Origin Set's size is unbounded by this specification, and thus The Origin Set's size is unbounded by this specification, and thus
could be used by attackers to exhaust client resources. To mitigate could be used by attackers to exhaust client resources. To mitigate
this risk, clients can monitor their state commitment and close the this risk, clients can monitor their state commitment and close the
connection if it is too high. connection if it is too high.
5. References 5. References
5.1. Normative References 5.1. Normative References
skipping to change at page 8, line 14threaded multi chat client server source code in c++ ¶ skipping to change at page 8, line 19chat application in c#.net source code ¶
[RFC6454] Barth, A., "The Web Origin Concept", RFC 6454, [RFC6454] Barth, A., "The Web Origin Concept", RFC 6454,
DOI 10.17487/RFC6454, December 2011, DOI 10.17487/RFC6454, December 2011,
<https://www.rfc-editor.org/info/rfc6454>. <https://www.rfc-editor.org/info/rfc6454>.
[RFC7540] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext [RFC7540] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext
Transfer Protocol Version 2 (HTTP/2)", RFC 7540, Transfer Protocol Version 2 (HTTP/2)", RFC 7540,
DOI 10.17487/RFC7540, May 2015, DOI 10.17487/RFC7540, May 2015,
<https://www.rfc-editor.org/info/rfc7540>. <https://www.rfc-editor.org/info/rfc7540>.
chat application in asp.net using c# source code [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
lan chat application in c# source code 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
android chat server source code May 2017, <https://www.rfc-editor.org/info/rfc8174>.
5.2. Informative References 5.2. Informative References
[RFC5988] Nottingham, M., "Web Linking", RFC 5988, [RFC5988] Nottingham, M., "Web Linking", RFC 5988,
DOI 10.17487/RFC5988, October 2010, DOI 10.17487/RFC5988, October 2010,
<https://www.rfc-editor.org/info/rfc5988>. <https://www.rfc-editor.org/info/rfc5988>.
[RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User [RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User
Service (RADIUS) Protocol Extensions", RFC 6929, Service (RADIUS) Protocol Extensions", RFC 6929,
DOI 10.17487/RFC6929, April 2013, DOI 10.17487/RFC6929, April 2013,
<https://www.rfc-editor.org/info/rfc6929>. <https://www.rfc-editor.org/info/rfc6929>.
skipping to change at page 9, line 45client server chat application android source code ¶ skipping to change at page 10, line 9chat server java source code ¶
obligated to use it, or to advertise all origins which they might be obligated to use it, or to advertise all origins which they might be
able to answer a request for. able to answer a request for.
For example, it can be used to inform the client that the connection For example, it can be used to inform the client that the connection
is to only be used for the SNI-based origin, by sending an empty is to only be used for the SNI-based origin, by sending an empty
ORIGIN frame. Or, a larger number of origins can be indicated by ORIGIN frame. Or, a larger number of origins can be indicated by
including a payload. including a payload.
Generally, this information is most useful to send before sending any Generally, this information is most useful to send before sending any
part of a response that might initiate a new connection; for example, part of a response that might initiate a new connection; for example,
"Link" headers [RFC5988] in a response HEADERS, or links in the "Link" headerchat bot source code c++ fields [RFC5988] in a response HEADERS, or links in the
response body. response body.
Therefore, the ORIGIN frame ought be sent as soon as possible on a Therefore, the ORIGIN frame ought be sent as soon as possible on a
connection, ideally before any HEADERS or PUSH_PROMISE frames. connection, ideally before any HEADERS or PUSH_PROMISE frames.
However, if it's desirable to associate a large number of origins However, if it's desirable to associate a large number of origins
with a connection, doing so might introduce end-user perceived with a connection, doing so might introduce end-user perceived
latency, due to their size. As a result, it might be necessary to latency, due to their size. As a result, it might be necessary to
select a "core" set of origins to send initially, expanding the set select a "core" set of origins to send initially, expanding the set
of origins the connection is used for with subsequent ORIGIN frames of origins the connection is used for with subsequent ORIGIN frames
later (e.g., when the connection is idle). later (e.g., when the connection is idle).
That said, senders are encouraged to include as many origins as That said, senders are encouraged to include as many origins as
practical within a single ORIGIN frame; clients need to make practical within a single ORIGIN frame; clients need to make
decisions about creating connections on the fly, and if the origin decisions about creating connections on the fly, and if the origin
set is split across many frames, their behaviour might be suboptimal. set is split across many frames, their behaviour might be suboptimal.
Senders take note that, as per eliza chatbot source code c++ [RFC6454] Section eliza chatterbot source code c++ 4, the values in an Senders take note that, as per Section chat application source code in java 4 of [RFC6454], the values in
ORIGIN header need to be case-normalised before serialisation. an ORIGIN header need to be case-normalised before serialisation.
Finally, servers that host alternative services [RFC7838] will need Finally, servers that host alternative services [RFC7838] will need
to explicitly advertise their origins when sending ORIGIN, because to explicitly advertise their origins when sending ORIGIN, because
the default contents of the Origin Set (as per Section 2.3) do not the default contents of the Origin Set (as per Section 2.3) do not
contain any Alternative Services' origins, even if they have been contain any Alternative Services' origins, even if they have been
used previously on the connection. used previously on the connection.
Authors' Addresses Authors' Addresses
Mark Nottingham Mark Nottingham
 End of changes. 22 change blocks. 
chat server project source code in java 55 lines changed or deletedchat source code in java chat source code in javascript 58 lines changed or added

This html diff was produced by rfcdiff 1.44jr. The latest version is available from live chat plugin for joomla 1.5