jshttp content-disposition issues

jshttp / content-disposition

Create and parse HTTP Content-Disposition header

MIT License

224 stars 43 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Refactor decodefield function and enhance JSDoc comments

#64 Ayoub-Mabrouk opened 1 day ago
0
Refactor format function: use destructuring, template literals, and for...of loop

#63 Ayoub-Mabrouk opened 1 day ago
0
refactor: modernize qstring function with ES6+ syntax

#62 Ayoub-Mabrouk opened 1 day ago
0
refactor: update ustring function with ES6+ syntax for improved readability

#61 Ayoub-Mabrouk opened 1 day ago
0
refactor: update contentDisposition function with ES6+ syntax for clarity

#60 Ayoub-Mabrouk opened 1 day ago
0
tests: Spelling

#59 jsoref closed 5 days ago
0
Release: 1.0.1

#58 UlisesGascon opened 2 weeks ago
4
Fix failing scorecard pipeline

#57 Phillip9587 opened 3 weeks ago
0
fix: update package.json engines field to reflect minimum supported node version

#56 Phillip9587 closed 1 week ago
0
Fix badges

#55 Phillip9587 opened 3 weeks ago
0
replace `mocha` and `nyc` with native node test runner and `c8`

#54 Phillip9587 opened 3 weeks ago
1
Remove dependency `safe-buffer`

#53 Phillip9587 closed 3 weeks ago
1
Ts/0.0.1

#52 ya-apl closed 1 month ago
2
1.x Staging PR

#51 wesleytodd closed 2 months ago
0
fix(ci)!:drop node <18 and update ci

#50 wesleytodd closed 2 months ago
0
Add OSSF scorecard pipeline

#49 carpasse closed 7 months ago
0
Fix CI GH action

#48 carpasse closed 7 months ago
1
Certain languages can't be matched correctly by the Regular Expression EXT_VALUE_REGEXP like en-US or zh_cn

#47 wally-li opened 1 year ago
3
Problems with supporting Cyrillic alphabet

#46 AIHI opened 1 year ago
5
Allow to be built with webpack, use only some features.

#45 ievgennaida closed 2 years ago
1
Remove use of Node.js modules

#44 zenflow closed 2 years ago
3
ISO-8859-1 (`ByteString`) is confused with ASCII string

#43 AlttiRi closed 2 years ago
5
Replace deprecated String.prototype.substr()

#42 CommanderRoot closed 3 months ago
0
Will this package ever hit a major version?

#40 rehanvdm closed 2 years ago
1
No matching version found for content-disposition@0.5.4.

#39 gorjan-mishevski closed 2 years ago
1
Tests using deep-equal won't fail

#38 alex7kom closed 2 years ago
1
Doesn't work anymore if path package is installed

#37 kud closed 3 years ago
8
Possibly address other control characters in header

#36 xavdid closed 3 years ago
2
Added power support for the travis.yml file with ppc64le

#35 sreekanth370 closed 3 years ago
1
change reg to match space in string

#34 sharh closed 4 years ago
1
should decode the header value

#33 sharh closed 4 years ago
1
Usage in browser. path and safe-buffer modules

#32 denis111 closed 4 years ago
3
filename not support chinese is become `????.epub`

#30 bluelovers closed 4 years ago
3
Fix typo in RFC (6987 --> 5987)

#29 fvoronin closed 3 years ago
1
filename* is not supported

#28 tiholic closed 5 years ago
2
Generate ext-parameter when utf8 and latin1 representations don't match

#27 jeremyspiegel opened 5 years ago
14
Remove safe-buffer, Update Supported Node Versions

#26 jharrilim closed 5 years ago
1
Is it safe to use with aws-sdk?

#25 emilsedgh closed 5 years ago
8
invalid parameter format with filename*=

#24 alexkli closed 5 years ago
2
BUG: "attachment; filename=@.xlsx" fails

#23 georgelviv closed 5 years ago
2
Feature request: browser support

#22 dessant closed 6 years ago
13
Avoid using deprecated Buffer API on newer Node.js

#21 ChALkeR closed 6 years ago
10
Allow for Non-Standard Charset Name

#20 s25g5d4 opened 6 years ago
1
"invalid parameter format" on trailing semicolon

#19 TanninOne closed 6 years ago
1
Added some docblocks to ContentDisposition class

#18 evert closed 6 years ago
0
Filename with square brackets throws exception

#17 Borewit closed 7 years ago
5
Extract filenames from RFC 2047 headers

#16 tusbar closed 7 years ago
3
allow parsing utf8 filenames

#15 5c077yP opened 7 years ago
1
Should `parse` fail when a parameter has non-decodable field?

#14 alexstrat closed 7 years ago
5
Support decode 'utf8' (no dash)

#13 alexstrat closed 2 months ago
14