Skip to content

Add Allow example for targetHints #675

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

Merged
merged 2 commits into from
Nov 21, 2018
Merged

Add Allow example for targetHints #675

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
749e8f8
Add Allow example for targetHints
handrews Nov 12, 2018
9e308cb
Fix example typo.
dlax Nov 13, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions jsonschema-hyperschema.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1470,6 +1470,29 @@ for varname in templateData:
In general, headers that are likely to have different values at different
times SHOULD NOT be included in "targetHints".
</t>
<figure>
<preamble>
As an example, an Allow header allowing HEAD, GET, and POST
would be shown as follows:
</preamble>
<artwork>
<![CDATA[
{
"targetHints": {
"allow": ["HEAD", "GET", "POST"]
}
}
]]>
</artwork>
<postamble>
Note that this is represented identically whether there is
a single-line Allow header with comma-separated values,
multiple Allow headers on separate lines, each with one value,
or any combination of such arrangements. As is generally true
with HTTP headers, comma-separated values and multiple occurrences
of the header are treated the same way.
</postamble>
</figure>
</section>
<section title='Advertising HTTP Features With "headerSchema"'>
<t>
Expand Down