Join GitHub today
multipart request: always skip boundary, fix #1220 #1221
I'd like to eventually add a validation that the
Aug 13, 2015
1 check passed
added a commit
this pull request
Aug 16, 2015
I thought about validation as in
Why doesn't you use SemVer normally? Just increase patch number and release new version. Because I can't really get this bug fix. I'm stuck with 3 options: use old 0.7.23 or use alpha tag or edit local source of 0.7.24. I like neither of this options.
Hm, I do intend to tag a new release shortly, but right now it doesn't make sense yet to switch to full SemVer (>=1.0.0), because more or less every release still contains some breaking changes or new features. But the plan is to split up the library into multiple pieces and tag some of them with a stable version shortly afterwards.
But you can safely use the alpha tag for now, as there are no critical changes and I will not introduce any of those until 0.7.25.
I'm receiving a EOF before end stream marker on this using the MultiPartPart script with FileMultiPart:
I don't add CRLF to the end boundary, so I'm wondering if the readLine is erroneous or if I should append CRLF.
According to RFC 1341 there is no CRLF required after the "--", so it looks like the correct thing to do would be to always read two bytes and require them to be either