Return-Path: X-Original-To: apmail-archiva-dev-archive@www.apache.org Delivered-To: apmail-archiva-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3D5761817B for ; Thu, 16 Jul 2015 20:23:05 +0000 (UTC) Received: (qmail 97000 invoked by uid 500); 16 Jul 2015 20:22:58 -0000 Delivered-To: apmail-archiva-dev-archive@archiva.apache.org Received: (qmail 96942 invoked by uid 500); 16 Jul 2015 20:22:58 -0000 Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@archiva.apache.org Delivered-To: mailing list dev@archiva.apache.org Received: (qmail 96931 invoked by uid 99); 16 Jul 2015 20:22:58 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jul 2015 20:22:58 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 47859E3AA1; Thu, 16 Jul 2015 20:22:58 +0000 (UTC) From: hugosenari To: dev@archiva.apache.org Reply-To: dev@archiva.apache.org References: In-Reply-To: Subject: [GitHub] archiva pull request: [MRM-1861] Proxy behaviour issue migrating f... Content-Type: text/plain Message-Id: <20150716202258.47859E3AA1@git1-us-west.apache.org> Date: Thu, 16 Jul 2015 20:22:58 +0000 (UTC) Github user hugosenari commented on the pull request: https://github.com/apache/archiva/pull/16#issuecomment-122078670 Only for the record. I tested this version (master), and don't solves my problem. I don't know if is another problem with proxy or is same that still unsolved. With old version my logs looks similar to bug description (timeout) now is different (auth error) If help, here is [my log](https://gist.github.com/hugosenari/3ffca9ddac4e3c5f256b). --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---