What are the ramifications of null bytes and multipart/form-data?

Nope, no transfer-encoding is needed (or ever used by browsers) on form-data. It's perfectly valid to include a run of 50 null bytes in a multipart/form-data value... indeed given that most binary files contain a lot of nulls that situation should arise as often as not with file uploads!

Nope, no transfer-encoding is needed (or ever used by browsers) on form-data. It's perfectly valid to include a run of 50 null bytes in a multipart/form-data value... indeed given that most binary files contain a lot of nulls that situation should arise as often as not with file uploads! Which makes me question whether it's really a Django bug, or whether there's not something else going on.

Let's have that stacktrace!

Not true. There is a "Content-Transfer-Encoding" header available, ie: "Content-Transfer-Encoding: binary". Or use "Content-Type: application/octet-stream" to send arbitrary data without interpretation.

– Remy Lebeau - TeamB Dec 18 '09 at 20:25 Content-Transfer-Encoding is not allowed in HTTP, see RFC2616 19.4.5. The encoding is always binary or an effective synonym. – bobince Dec 19 '09 at 3:16.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.