Examples vs. syntax spec inconsistencies about hrx HOT 2 CLOSED

I just want to be on the same page here with those other two parsers, just so I can catch any significant spec-violating they're doing. I tried to make them to be a bit more tolerant of mistakes.

So if I'm understanding correctly, this tends to show up on empty files. They're looking for a LF then a boundary to end the file, but there's no LF, there's just a boundary.

body is optional, however determining whether body is file contents or a continuation of the archive (in the case of empty files)

I feel that the spec should cover something such that a content block shouldn't begin with a boundary of the current size the parser is processing, which is probably why my parsers didn't catch it.

from hrx.

Good catches! They all seem right, and @rebeccajae is correct that the spec should forbid a contents production that starts with a boundary. I'll put out a fix.

from hrx.