On a vivoactive, when a remote service returns a 401 HTTP code, I'm seeing it appear as a -300 (NETWORK_REQUEST_TIMED_OUT) error. It doesn't appear the request is really timing out, because 200 OK's with a much bigger payload are succeeding just fine.
Anyone else seeing this?
(I think the workaround for now will be for all requests to return a 200 at the HTTP transport level, and return a separate application status as part of the payload).