pillarjs / pillarjs/multiparty
content-disposition is optional for multipart/related
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 164
- Avg merge
- 4h 16m
- Merged PRs (30d)
- 4
Description
According https://tools.ietf.org/html/rfc2387#section-4 on multipart/related content-disposition header is optional.
Library only grab a file if content-disposition exists.
I think library should be able to handle files without this optional header and save it with a random (based on timestamp for example) filename.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the library's multipart/related handling and the point where content-disposition is required. Compare that behavior with the RFC 2387 requirement that the header is optional, then verify that a part without it is retained with a generated filename. The payload names no source files or tests, so those will need to be located first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100