Update lib/incoming_form.js #163
Closed
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
bug with content-disposition when name comes after filename. This is due to regex for name matches "filename" too..
|
@jesperp Any news? |
egirshov
added a commit
to egirshov/node-formidable
that referenced
this pull request
Feb 6, 2013
|
Sorry @Jellyfrog I've been away for a while so haven't looked into this, but looks like @egirshov finalized it. Thanks egirshov! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
bug with content-disposition when name comes after filename. E.g:
This will set part.name to "test/x.png" instead of files[] because the regex to search for "name=" matches filename= first. The order of name/filename should not matter to the user :)
Solution is simple, add a \b (word boundary) to regex for name/filename..