Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ORIGIN-compliant clients and legacy servers #438

Closed
MikeBishop opened this issue Nov 28, 2017 · 0 comments
Closed

ORIGIN-compliant clients and legacy servers #438

MikeBishop opened this issue Nov 28, 2017 · 0 comments

Comments

@MikeBishop
Copy link
Contributor

The text in 2.4 says....

Once an Origin Set has been initialized... [lots of stuff]

Additionally, clients MAY avoid consulting DNS to establish the connection’s authority for new requests; however, those that do so face new risks, as explained in Section 4.

I think part of our issue with how Edge implemented coalescing without considering DNS arises from the fact that this "Additionally" isn't clearly tied to being something that clients do "Once an Origin Set has been initialized" versus something that clients do in addition to the above behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MikeBishop