No, it was http 401, exactly same problem as described in the first post of this thread.