72a87dfb2d
* fix: ensure binary events can handle no content-type header The fix provided in https://github.com/cloudevents/sdk-javascript/pull/118 only included tests for `receiver.check()`, and the change in that case was to add the `application/json` content type to the cleansed headers if to type was specified. However, `receiver.parse()` did not receive the benefit of this change. It calls `this.check()` but then sanitizes the original headers again, and the missing content-type was not re-inserted into the newly sanitized headers. This commit, modifies the code so that `receiver.check()` does not insert the content-type, but does allow the validation check to pass if no content-type header exists. When `receiver.parse()` is called, and the headers are sanitized again - and this time used to look up parser implementation, the default `application/json` content-is applied if no content-type header exists. I've also removed a redundant call to `receiver.check()` in receiver_binary_1.js and simplified the usage of `Constants` in the test. Signed-off-by: Lance Ball <lball@redhat.com> * chore: clean up header sniffing Signed-off-by: Lance Ball <lball@redhat.com> |
||
|---|---|---|
| .. | ||
| bindings/http | ||
| formats/json | ||
| fun_tests.js | ||
| http_binding_0_3.js | ||
| http_binding_1.js | ||
| sdk_test.js | ||
| spec_0_3_tests.js | ||
| spec_1_tests.js | ||