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.

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

Move an implementation note out of the summary #626

Merged
merged 1 commit into from
Sep 11, 2024
Merged

Move an implementation note out of the summary #626

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
18 changes: 9 additions & 9 deletions steps/src/main/xml/steps/http-request.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,7 @@
with resources over HTTP or related protocols. Implementations
<rfc2119>must</rfc2119> support the <literal>http</literal> and
<literal>https</literal> protocols.
(Implementors are encouraged to support as many protocols as
practical. In particular, pipeline authors may attempt to use
<tag>p:http-request</tag> to load documents with computed URIs using
the <literal>file:</literal> scheme.)</para>
</para>

<p:declare-step type="p:http-request">
<p:input port="source" content-types="any" sequence="true"/>
Expand All @@ -28,11 +25,14 @@ the <literal>file:</literal> scheme.)</para>
<p:option name="assert" as="xs:string" select="'.?status-code lt 400'" />
</p:declare-step>

<para>The <tag>p:http-request</tag> step performs the HTTP request
specified by the <option>method</option> option against the URI specified in
the <option>href</option> option. In simple cases, for example, a GET
request on an unauthenticated URI, nothing else is necessary to form a
complete request.</para>
<para>The <tag>p:http-request</tag> step performs the HTTP request specified by
the <option>method</option> option against the URI specified in the
<option>href</option> option. In simple cases, for example, a GET request on an
unauthenticated URI, nothing else is necessary to form a complete request.
(Implementors are encouraged to support as many protocols as practical. In
particular, pipeline authors may attempt to use <tag>p:http-request</tag> to
load documents with computed URIs using the <literal>file:</literal> scheme.)
</para>

<para>If the method, for example, POST, supports a body, the request
body is constructed using the document(s) appearing on the
Expand Down