You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 5, 2023. It is now read-only.
Task #101 will implement a naive approach to parsing the capability-invocation header on HTTP requests. The approach does not account for subtle differences in the value of the header when, for instance, the same header is present multiple times in a request, or if there is whitespace around some identifiers/values.
A big part of the problem here is that the syntax of the capability-invocation header is not defined. As a matter of fact, the header itself is not defined anywhere.
The text was updated successfully, but these errors were encountered:
Task #101 will implement a naive approach to parsing the
capability-invocation
header on HTTP requests. The approach does not account for subtle differences in the value of the header when, for instance, the same header is present multiple times in a request, or if there is whitespace around some identifiers/values.A big part of the problem here is that the syntax of the
capability-invocation
header is not defined. As a matter of fact, the header itself is not defined anywhere.The text was updated successfully, but these errors were encountered: