issues
search
jshttp
/
content-type
Create and parse HTTP Content-Type header
MIT License
131
stars
27
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Update version-history.js
#28
samss084
closed
1 week ago
0
v2.0.0 - Major Release (Proposal)
#27
Phillip9587
opened
1 month ago
4
v2.0.0 - Major Release (Proposal)
#26
Phillip9587
closed
1 month ago
5
Does not throw on some incorrect headers
#25
wesleytodd
closed
3 months ago
10
Replace deep-equal with dequal
#24
wojtekmaj
opened
4 months ago
3
Add ossf scorecard pipeline
#23
carpasse
closed
7 months ago
0
Fix ci GH action
#22
carpasse
closed
7 months ago
0
lchown /node_modules/content-type/HISTORY.md: invalid argument.
#21
playground
closed
1 year ago
9
Replace deprecated String.prototype.substr()
#20
CommanderRoot
closed
1 year ago
0
Also a valid way to present the Content-type header
#18
gregz07
closed
3 years ago
7
Added power support for the travis.yml file with ppc64le.
#17
sreekanth370
closed
3 years ago
1
Black Duck reporting Thunderbird as a dependency to content-type npm package
#16
adityachava2022
closed
4 years ago
1
[Bug] Throw invalid parameter format error when no charset property
#15
alberthuang24
closed
4 years ago
2
remove "bad" whitespace !
#14
murataka
closed
5 years ago
6
doc: improve contentType.format and expression
#13
marswong
closed
6 years ago
0
FIX: When property value contains forwardslash
#12
srolija
closed
7 years ago
5
Update typeRegExp docstring to reflect implementation
#11
bbamsch
closed
7 years ago
2
Content-Type checking less restrictive than RFC 6838 spec
#10
bbamsch
closed
7 years ago
4
Invalid parameter format reading Amazon AVS multipart headers
#9
Mnark
closed
8 years ago
1
What happens if there is no encoding specified?
#8
loong
closed
8 years ago
3
Make Lib Browser Compatible
#7
maennchen
closed
8 years ago
16
Do you need to `type.toLowerCase()`?
#6
akhoury
closed
8 years ago
3
Accept slashes in parameter values
#5
gwicke
closed
8 years ago
9
how to catch parsing errors
#4
thisconnect
closed
9 years ago
3
Check module node.js 4.* to raise in express.js
#3
nook-scheel
closed
9 years ago
0
double quotes seemingly required for profile parameter
#2
howarddierking
closed
9 years ago
4
Add documentation on error handling, specify missing header in error message
#1
gr0uch
closed
9 years ago
11