Skip to content

Commit

Permalink
spec: Allow text/html success response for Seed Report endpoint
Browse files Browse the repository at this point in the history
There is no particular reason to limit the Seed Report endpoint to
returning a human-readable message only in the error case.  Allow an
HTML response body for both success and error response codes.

Suggested-by: David Spence <[email protected]>
Signed-off-by: Michael Brown <[email protected]>
  • Loading branch information
mcb30 committed Apr 28, 2020
1 parent af1dc11 commit 78453a2
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions spec/cx.lyx
Original file line number Diff line number Diff line change
Expand Up @@ -8605,12 +8605,11 @@ Response
\begin_inset space ~
\end_inset

Content-Type: text/html (in the case of an error status code)
Content-Type: text/html (or empty response)
\end_layout

\begin_layout Description
Response Status code only, with a human-readable HTML error description
in the case of an error status code.
Response Status code plus OPTIONAL human-readable message in HTML format
\end_layout

\begin_layout Standard
Expand Down Expand Up @@ -8644,8 +8643,10 @@ An Advertiser SHALL refuse to attempt to retrieve content from this endpoint

\begin_layout Standard
An Advertiser SHALL provide an indication to the user as to whether or not
the reponse was successful, and SHOULD provide an opportunity for the user
to view the HTML error description if the response was not successful.
the reponse was successful, SHOULD provide an opportunity for the user
to view the HTML error message if the response was not successful, and
MAY provide an opportunity for the user to view the HTML message if the
response was successful.
\end_layout

\begin_layout Subsection
Expand Down

0 comments on commit 78453a2

Please sign in to comment.