libwww-perl / libwww-perl/HTTP-Message
Filename is not parsed correctly
Open
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 32
- Forks
- 63
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 1
Description
Suppose the server hands us the following Content-Disposition:
attachment; filename*=UTF-8''file.txt;
Then we should get a filename of "file.txt", but we get no file name at all.
Contributor guide
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 locating the Content-Disposition parser and reproduce the issue with the provided UTF-8 filename* header. Done means the parser returns "file.txt" instead of no filename; add or run the relevant parsing test if the repository provides one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100