6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
9/4/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#12161] Unable to parse certain multi-part messages
*
Your Email Address
*
Spam protection
Enter the letters below:
.__.. ..__ . ..___. [__]|__|[__)\ / | | || |[__) \/ |
Comment
> The Boundary parameter of the Content-Type header has an uppercase B, > however per section 2 of RFC 2045 > (http://tools.ietf.org/html/rfc2045#section-2): > > All numeric and octet values are given in decimal notation in this > set of documents. All media type values, subtype values, and > parameter names as defined are case-insensitive. However, parameter > values are case-sensitive unless otherwise specified for the specific > parameter. > > Will provide unit tests and a patch on Github to resolve this issue >
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers