Bug: parser cannot handle unexpected text Content-Type.
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
Some (old) ASF messages [1,2] have unexpected Content-type, for example:
Content-Type: text/$email_type; charset=iso-8859-1
Whilst this is not strictly valid, it's clearly a text message.
At present the message is dropped.
[1] http://mail-archives.apache.org/mod_mbox/jakarta-general/200301.mbox/%3C1631.192.193.196.3.1043161136.squirrel@duckmail.d2g.com%3E
[2] http://mail-archives.apache.org/mod_mbox/jakarta-general/200301.mbox/%3C7703.192.193.196.9.1043165745.squirrel@duckmail.d2g.com%3E
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no file or test. Start by locating the JavaScript parser path that classifies Content-Type values, then reproduce the sample header and trace why the message is dropped. Done means ASF messages with this malformed text content type are retained as text, with a regression test covering the example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100