Test of pipeline 1 from the #45 with invalid pipeline failed

[m1ci]

e-Entity -> e-Link

curl -v -d @pipeline1.json -X POST -H "Content-Type: application/json" "http://localhost:8080/pipelining/chain"

pipeline1.json is the same e-Entity -> e-Link pipeline from the documentation with only changed the “headers” part to:

"hea": {
    "ctent-type": "texain",
    "acpt": "texurtle"
},

Results:

• no error returned that “hea” should not be part of pipeline definition
• also, if we set correct value of the headers part but invalid headers, still no error returned. Maybe this should be as it is, since the headers defined by a service are unknown in advance to be validated.

Example:

"header": {
    "ctent-type": "texain",
    "acpt": "texurtle"
},

[ghsnd]

The first issue should be adressed, I agree (will let you know if it's fixed). As for the second: pure technically, you can insert whatever you want as header into an HTTP request, as long as it obeys the format. It is a good question to see if it is up to the pipelining service to check that. Personally I think it is up to the service in question to check headers / content and reply with an error.

[m1ci]

The first issue should be adressed, I agree (will let you know if it's fixed).

OK

As for the second: pure technically, you can insert whatever you want as header into an HTTP request, as long as it obeys the format. It is a good question to see if it is up to the pipelining service to check that. Personally I think it is up to the service in question to check headers / content and reply with an error.

I agree.

[ghsnd]

Issue 1 should be fixed: in the case of the example, the response body is:

{
  "exception": "eu.freme.broker.exception.NotAcceptableException",
  "path": "/pipelining/chain",
  "message": "Error detected in the JSON body contents: Request 1: field \"hea\" not known.",
  "error": "Not Acceptable",
  "status": 406,
  "timestamp": 1440081037672
}

Can you re-test ?

[m1ci]

test passed, well done!