OData / OData/odataorg.github.io

TripPin OData v4 Sample Service: Bug in Batch support

Open
#123 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
73
Forks
106
PR merge metrics
No merged PRs in 30d

Description

Hi!

When sending the following batch request:

POST http://services.odata.org/TripPinRESTierService/(S(44nbzk0kapmsdmankuj0auq0))/$batch

OData-Version:4.0
Content-Type:multipart/mixed; boundary=batch_id-1486480047107-5

--batch_id-1486480047107-5
Content-Type:application/http
Content-Transfer-Encoding:binary

GET Airlines?$skip=0&$top=100 HTTP/1.1
Accept:application/json;odata.metadata=minimal;IEEE754Compatible=true
Accept-Language:de-DE
Content-Type:application/json;charset=UTF-8;IEEE754Compatible=true
--batch_id-1486480047107-5--

... I get the following error response, instead of the requested data:

--batchresponse_c8665a96-5705-4304-ac6c-db090c6b5d47
Content-Type: application/http
Content-Transfer-Encoding: binary

HTTP/1.1 404 Not Found
Content-Type: application/json; charset=utf-8

{"Message":"No HTTP resource was found that matches the request URI 'http://services.odata.org/TripPinRESTierService/(S(44nbzk0kapmsdmankuj0auq0))/Airlines?$skip=0&$top=100'."}
--batchresponse_c8665a96-5705-4304-ac6c-db090c6b5d47--

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the batch request shown in the issue against the TripPinRESTierService $batch endpoint and compare the 404 response with the requested Airlines data. Trace how the sample service handles the batch request and verify that the same request returns the requested data instead of a 404.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.