Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

expose filename and headers for streams in a multipart form #1525

Merged
merged 1 commit into from
Mar 29, 2014

Conversation

nlf
Copy link
Member

@nlf nlf commented Mar 25, 2014

This provides some knowledge about the streams in a multipart form to the user.

@petreboy14
Copy link

👍

@@ -509,7 +509,7 @@ The following options are available when adding a route:
multipart) based on the 'Content-Type' header. If `parse` is false, the raw `Buffer` is returned. This is the default value
except when a proxy handler is used.
- `stream` - the incoming payload is made available via a `Stream.Readable` interface. If the payload is 'multipart/form-data' and
`parse` is `true`, fields values are presented as text while files are provided as streams.
`parse` is `true`, fields values are presented as text while files are provided as streams. File streams from a 'multipart/form-data' upload will also have a property `.hapi` containing `filename` and `headers` properties.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the future, we add manual line breaks to docs.

@hueniverse hueniverse added this to the 3.1.0 milestone Mar 29, 2014
@hueniverse hueniverse self-assigned this Mar 29, 2014
hueniverse pushed a commit that referenced this pull request Mar 29, 2014
expose filename and headers for streams in a multipart form
@hueniverse hueniverse merged commit 2e24842 into hapijs:master Mar 29, 2014
hueniverse pushed a commit that referenced this pull request Mar 29, 2014
@lock lock bot locked as resolved and limited conversation to collaborators Jan 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature New functionality or improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants