Adding support for unusual 'Content-Encoding: none' header about mechanize HOT 2 CLOSED

likewise-- I'm hitting a page (Atlassian's JIRA) that is returning a blank Content-Encoding. I'd love it if empty content-encoding also did the same thing as if there were none specified at all -- it could be a very similar patch to this. Or maybe keep a list of known "encodings" that should just do the default behavior ('none' and '')

from mechanize.

Personally, I don't see why it couldn't be just:

when 'gzip'
  # gzip stuff
else
  body.read

I can't think of any other encodings that need special decoding, and it certainly doesn't do any others at present, but there's clearly a few servers out there that produce invalid encodings, and this would remove the need to keep adding extra ones. Could always add known invalid ones and just raise unsupported errors for those.

from mechanize.