-
In the Subtype entry of Table 44 (section 7.4.11.1), we have:
"_The value of this entry shall conform to the MIME media type names defined in Internet RFC 2046, with the provision that characters not…
-
https://github.com/camcima/php-mysql-diff/blob/a12f9648b9948827800dad41c62616088e4dcd10/src/RegExpPattern.php#L38
Because you replace comments with base64. Read RFC 2045. '/' is 63 symbol in Base64…
Enyby updated
4 years ago
-
While the value can be parsed under RFC 2045, it is problematic when using a stricter RFC 4648 coder, such as Ruby's `urlsafe_decode64` or `strict_decode64`, as the test vector cannot exercise the int…
-
```
The current implementation was recently changed to escape "=" characters
as "\=" in the "boundary" parameter of the "Content-Type" header for MIME
emails. This appears to be wrong behavior. Ne…
-
mime-types was "built to conform to the MIME types of RFCs 2045 and 2231". RFC 2045 is itself composed of many other RFCs, some of which have been obsoleted or updated. For example, it refers to [RFC …
-
It appears some rfc referenced in the 2x specification and CDMI extension documents may have been updated. We should consider an audit on impacts, if any, to the cdmi 2x specification and associated e…
-
Hello,
we encountered an issue when sending multipart emails (html and text) with a lot of content.
There either random spaces inside the source code of the mail or broken characters because of in…
-
```
The current implementation was recently changed to escape "=" characters
as "\=" in the "boundary" parameter of the "Content-Type" header for MIME
emails. This appears to be wrong behavior. Ne…
-
Add support for
-
Reference to 430-2