Proper Content-Type header on CCIP POST requests #2876
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, CCIP POST requests are sent without
Content-Type
headers, which makes requests fail for servers that reject the body if the header isn't present.PR-Codex overview
This PR focuses on enhancing the CCIP functionality by ensuring that
POST
requests include the appropriateContent-Type
header, which is essential for correctly indicating the format of the data being sent.Detailed summary
ccip.ts
file, aheaders
object is created forPOST
requests, settingContent-Type
toapplication/json
.fetch
call is updated to include the newly createdheaders
object.