You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Indico 3.1 does not specify the charset parameter in an iCalendar event attached to reminder email. More precisely, it seems to misname the parameter encoding.
To Reproduce
Steps to reproduce the behavior:
Create an event
Add a reminder
Check the "Attach iCalendar file" option
Receive the reminder email
Some applications fail to handle the iCalendar event in the message
Expected behavior
The iCalendar event is expected to be displayed by the email application.
Additional context Section 3.1.4 of RFC5545 requires the charset Content-Type parameter in MIME transports. See also the errata. This rule was obeyed by previous releases of indico as the following MIME part shows:
Describe the bug
Indico 3.1 does not specify the
charset
parameter in an iCalendar event attached to reminder email. More precisely, it seems to misname the parameterencoding
.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The iCalendar event is expected to be displayed by the email application.
Additional context
Section 3.1.4 of RFC5545 requires the
charset
Content-Type parameter in MIME transports. See also the errata. This rule was obeyed by previous releases of indico as the following MIME part shows:This is no longer the case as of version 3.1:
Another parameter called
encoding
is set toutf-8
instead.The text was updated successfully, but these errors were encountered: