jshttp/content-type issues and pull requests

#23 - Add ossf scorecard pipeline

Pull Request - State: closed - Opened by carpasse 3 months ago

#22 - Fix ci GH action

Pull Request - State: closed - Opened by carpasse 3 months ago

#21 - lchown /node_modules/content-type/HISTORY.md: invalid argument.

Issue - State: closed - Opened by playground over 1 year ago - 9 comments

#20 - Replace deprecated String.prototype.substr()

Pull Request - State: closed - Opened by CommanderRoot over 2 years ago
Labels: pr

#18 - Also a valid way to present the Content-type header

Issue - State: closed - Opened by gregz07 almost 3 years ago - 7 comments

#17 - Added power support for the travis.yml file with ppc64le.

Pull Request - State: closed - Opened by sreekanth370 over 3 years ago - 1 comment
Labels: pr

#16 - Black Duck reporting Thunderbird as a dependency to content-type npm package

Issue - State: closed - Opened by adityachava2022 almost 4 years ago - 1 comment
Labels: question

#15 - [Bug] Throw invalid parameter format error when no charset property

Issue - State: closed - Opened by alberthuang24 about 4 years ago - 2 comments
Labels: invalid

#14 - remove "bad" whitespace !

Pull Request - State: closed - Opened by murataka almost 5 years ago - 6 comments
Labels: invalid, pr

#13 - doc: improve contentType.format and expression

Pull Request - State: closed - Opened by marswong over 6 years ago
Labels: docs, pr

#12 - FIX: When property value contains forwardslash

Pull Request - State: closed - Opened by srolija about 7 years ago - 5 comments
Labels: invalid, pr

#11 - Update typeRegExp docstring to reflect implementation

Pull Request - State: closed - Opened by bbamsch over 7 years ago - 2 comments
Labels: pr

#10 - Content-Type checking less restrictive than RFC 6838 spec

Issue - State: closed - Opened by bbamsch over 7 years ago - 4 comments
Labels: question

#9 - Invalid parameter format reading Amazon AVS multipart headers

Issue - State: closed - Opened by Mnark almost 8 years ago - 1 comment
Labels: question

#8 - What happens if there is no encoding specified?

Issue - State: closed - Opened by loong almost 8 years ago - 3 comments
Labels: question

#7 - Make Lib Browser Compatible

Pull Request - State: closed - Opened by maennchen over 8 years ago - 16 comments
Labels: wontfix, needs tests, pr

#6 - Do you need to `type.toLowerCase()`?

Issue - State: closed - Opened by akhoury over 8 years ago - 3 comments
Labels: question

#5 - Accept slashes in parameter values

Pull Request - State: closed - Opened by gwicke over 8 years ago - 9 comments
Labels: discuss, needs tests, pr

#4 - how to catch parsing errors

Issue - State: closed - Opened by thisconnect almost 9 years ago - 3 comments
Labels: question

#3 - Check module node.js 4.* to raise in express.js

Pull Request - State: closed - Opened by nook-scheel almost 9 years ago
Labels: pr

#2 - double quotes seemingly required for profile parameter

Issue - State: closed - Opened by howarddierking about 9 years ago - 4 comments
Labels: question

#1 - Add documentation on error handling, specify missing header in error message

Pull Request - State: closed - Opened by gr0uch over 9 years ago - 11 comments

Ecosyste.ms: Issues

GitHub / jshttp/content-type issues and pull requests