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

GOAWAY vs logging #197

Closed
reschke opened this issue Aug 6, 2013 · 1 comment
Closed

GOAWAY vs logging #197

reschke opened this issue Aug 6, 2013 · 1 comment

Comments

@reschke
Copy link
Contributor

reschke commented Aug 6, 2013

6.8:

"Endpoints MAY append opaque data to the payload of any GOAWAY frame. Additional debug data is intended for diagnostic purposes only and carries no semantic value. Debug data MUST NOT be persistently stored, since it could contain sensitive information."

Read literally this means it can't be logged; do we really mean that? Do we expect this advice will be followed? Maybe this needs to be made clearer.

@martinthomson
Copy link
Collaborator

Clearer in what way? The problem here is that the information potentially contains sensitive data (PII, etc...) Is there something we can do with respect to 2119 language (i.e., not using MUST/NOT) that would make this clearer?

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

No branches or pull requests

2 participants