Comment 10 for bug 1559072

I've opened an issue against webob:

I doubt they are going to change it since it's fixing a long standing behavior issue, but it was a backward incompatible change and probably should have gone out in a major version 2.0 release.

But we'll probably need to cap webob<1.6.0 until the various clients are working with this.