I don't know where you guys landed on this issues, or whether or not you even think embedded nulls are an error. Nonetheless, here's a page that demonstrates embedded nulls being passed from necko to the parser. Note: I've added lots of defensive code to the scanner to detect and correct this problem, so it's not a huge issue. More of an FYI.
I thought we determined that this happened when the server sent a bad content-length, and they were usually the last character(s) in the document. Is this a different case? BTW, this is a dup.
Bulk move of all Necko (to be deleted component) bugs to new Networking component.
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 12415 ***
Read 12415 and this is a dup of it. Marking as VERIFIED.
You need to log in before you can comment on or make changes to this bug.