OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (ODATA-1405) /$query shall allow Content-Type: application/x-www-form-urlencoded

Heiko created ODATA-1405:

             Summary: /$query shall allow Content-Type: application/x-www-form-urlencoded
                 Key: ODATA-1405
                 URL: https://issues.oasis-open.org/browse/ODATA-1405
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
            Reporter: Heiko

An HTML form can be used to have a browser _navigate_ to the response of an OData request, especially if the response is a stream. If that OData request makes use of the [{{/$query}}|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_PassingQueryOptionsintheRequestBody] segment, it must have {{Content-Type: text/plain}}, which forces an HTML form like
<form method="post" enctype="text/plain">
 <input name="$filter" value="a%20eq%201&$select=b"/>

Much more natural would be if {{Content-Type: application/x-www-form-urlencoded}} were also allowed:
<form method="post" enctype="application/x-www-form-urlencoded">
 <input name="$filter" value="a eq 1"/>
 <input name="$select" value="b"/>

This message was sent by Atlassian Jira

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]