ok.. just figured out what is happening. ResponseErrorHandler is not used when there are connection issues. Only response issues. The timing of the app changed such that pre-filtering based on connection was not as accurate and hence there was a chance of a connection throwing an exception. There is no way to stop connection issues from thowing an exception other than adding some kind of localhost Proxy via HttpConnectionFactory which I'm going to avoid. Sorry for that.