Giters
jshttp
/
content-disposition
Create and parse HTTP Content-Disposition header
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
218
Watchers:
13
Issues:
32
Forks:
38
jshttp/content-disposition Issues
Certain languages can't be matched correctly by the Regular Expression EXT_VALUE_REGEXP like en-US or zh_cn
Updated
a year ago
Comments count
3
Problems with supporting Cyrillic alphabet
Updated
a year ago
Comments count
5
Usage in browser. path and safe-buffer modules
Closed
4 years ago
Comments count
3
Allow to be built with webpack, use only some features.
Closed
2 years ago
Comments count
1
Remove use of Node.js modules
Closed
2 years ago
Comments count
3
ISO-8859-1 (`ByteString`) is confused with ASCII string
Closed
2 years ago
Comments count
5
Will this package ever hit a major version?
Closed
2 years ago
Comments count
1
No matching version found for content-disposition@0.5.4.
Closed
2 years ago
Comments count
1
Tests using deep-equal won't fail
Closed
2 years ago
Comments count
1
Doesn't work anymore if path package is installed
Closed
3 years ago
Comments count
8
Possibly address other control characters in header
Closed
3 years ago
Comments count
2
Better multipart support
Updated
4 years ago
Comments count
3
should decode the header value
Closed
4 years ago
Comments count
1
Feature request: browser support
Closed
6 years ago
Comments count
13
filename not support chinese is become `????.epub`
Closed
4 years ago
Comments count
3
filename* is not supported
Closed
5 years ago
Comments count
2
Generate ext-parameter when utf8 and latin1 representations don't match
Updated
5 years ago
Comments count
14
Is it safe to use with aws-sdk?
Closed
5 years ago
Comments count
8
invalid parameter format with filename*=
Closed
5 years ago
Comments count
2
BUG: "attachment; filename=@.xlsx" fails
Closed
5 years ago
Comments count
2
Allow for Non-Standard Charset Name
Updated
6 years ago
Comments count
1
Filename with square brackets throws exception
Closed
7 years ago
Comments count
5
"invalid parameter format" on trailing semicolon
Closed
6 years ago
Comments count
1
allow parsing utf8 filenames
Updated
7 years ago
Comments count
1
Should `parse` fail when a parameter has non-decodable field?
Closed
7 years ago
Comments count
5
Parsing with tab character throws
Closed
7 years ago
Comments count
3
error parse when have semicolon at last
Closed
8 years ago
Comments count
3
Many servers return content-disposition with a trailing semicolon.
Closed
8 years ago
Comments count
3
Throwing an error during parsing
Closed
8 years ago
Comments count
1
Filename field does not support parenthesis
Closed
8 years ago
Comments count
3
Support continuations
Updated
9 years ago
Comments count
3
parsing content-disposition headers?
Closed
10 years ago
Comments count
8