[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1589) /$query shall allow Content-Type: application/json
Heiko Theissen created ODATA-1589: ------------------------------------- Summary: /$query shall allow Content-Type: application/json Key: ODATA-1589 URL: https://issues.oasis-open.org/browse/ODATA-1589 Project: OASIS Open Data Protocol (OData) TC Issue Type: Improvement Components: URL Conventions Affects Versions: V4.01_OS Environment: Proposed Reporter: Heiko Theissen Assignee: Heiko Theissen Fix For: V4.02 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 {code:xml} <form method="post" enctype="text/plain"> <input name="$filter" value="a%20eq%201&$select=b"/> </form> {code} Much more natural would be if {{Content-Type: application/x-www-form-urlencoded}} were also allowed: {code:xml} <form method="post" enctype="application/x-www-form-urlencoded"> <input name="$filter" value="a eq 1"/> <input name="$select" value="b"/> </form> {code} -- This message was sent by Atlassian Jira (v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]