Ah, OK. So the underlying problem is that we are setting Expect: 100 by default in the first place (I recall the discussion) and, pending a solution for that, the workaround _here_ is to prevent any problems from occurring.

For this test, though, aren't we able to predict the expected responses? I mean, should we be getting a 401 here in the first place? Or is the fix simply to make debugging easier so that if we _don't_ get a 100, we can more easily see what _actually_ happened?