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.

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

SETTINGS persistence #8

Closed
mnot opened this issue Feb 7, 2013 · 3 comments · Fixed by #796
Closed

SETTINGS persistence #8

mnot opened this issue Feb 7, 2013 · 3 comments · Fixed by #796

Comments

@mnot
Copy link
Member

mnot commented Feb 7, 2013

From the SPDY draft:

""A SETTINGS frame [...]. When the server is the sender, the sender can request that configuration data be persisted by the client across SPDY sessions and returned to the server in future communications.""

The concern here is that this provides another mechanism by which servers are able to track clients.

See also ​http://lists.w3.org/Archives/Public/ietf-http-wg/2012OctDec/0495.html

@mnot
Copy link
Member Author

mnot commented Jun 13, 2013

Discussed at SF Interim; general feeling is that settings persisitence is not the best way to achieve the goal (DoS mitigation). James to propose a new "reconnect with last settings" GOAWAY flag; Gabriel to look into ALPN settings communication (as well as Upgrade).

@mnot
Copy link
Member Author

mnot commented Jun 14, 2013

... however, it WOULD be required for CWND setting (if we choose to re-add it).

@mnot
Copy link
Member Author

mnot commented Jun 14, 2013

Remove settings persistence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant