Comment 2 for bug 1183169

Yeah, I agree the response change isn't right. The xml response changed too, of course. I'm actually surprised my Swiftly handled this okay; I must've had a similar situation somewhere else in Swift before.

Anyway, this should be fixed before the next "official" release, so I'm going to up the levels or whatever. Maybe Hadas would like to tackle this since he was just in there?