> I've had some problems with messages which doesn't follow the RFC when
> regarding to parameter building. More specificaly, I've found the
> following header in a message (in one line):
[...]
Never mind. I've just read your announce:
---
- More liberal acceptance of parameter formatting, e.g. this is
now accepted: Content-Type: multipart/mixed; boundary = "FOO"
I.e. spaces around the = sign.
---
Thank you!
--
Gustavo Niemeyer
[ 2AAC 7928 0FBF 0299 5EB5 60E2 2253 B29A 6664 3A0C ]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4