Clarified the format of payload in server.inject in the Reference doc #820
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It doesn't have to be a JSON string. It can be any string or any buffer. The key is that if you have an object, you have to stringify it yourself. Feel free to adjust the language to reflect that and I'll merge. |
|
That wasn't what I was seeing (every other format gave a 400 'Invalid request payload format') , but I've just found out that was due to the fact I hadn't specified a content-type in the injected request headers. I'll change the wording. |
hueniverse
pushed a commit
that referenced
this pull request
May 7, 2013
Clarified the format of payload in server.inject in the Reference doc
jmonster
pushed a commit
to jmonster/hapi
that referenced
this pull request
Feb 10, 2014
…ify-docs Clarified the format of payload in server.inject in the Reference doc
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
It wasn't clear from the docs what format the payload needed to be in for a POST request. This is a tiny trivial change to the ref doc to make that clear.