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

Discuss possible generic defenses #2

Open

chris-wood opened this issue Jan 20, 2020 · 0 comments

Collaborator

chris-wood commented Jan 20, 2020 •

edited

From @sftcd,

A suggested addition to section 7: What mechanisms
to counter WF might make sense for generic libraries
(e.g. TLS/HTTP libraries) and HTTP servers? By "generic"
here I mean code that doesn't know anything about the
resources will be served/consumed. And in saying
"mechanisms" I include APIs and controls that turn on
or off or configure protocol-level anti-WF schemes.

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