Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (nike.apache.org: domain of antoine@gmx.de designates
 212.227.15.19 as permitted sender)
From: Antoine Levy Lambert <antoine@gmx.de>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_1C95375E-E8AB-4A52-8BD1-48D748D68F2E"
Message-Id: <66FD4078-DD84-49D0-AC5E-56D82A8241DF@gmx.de>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: issue with IBiblioResolverTest.testErrorReport
Date: Mon, 26 Jan 2015 18:05:48 -0500
References: <3FC926F6-DAC3-4E22-948C-AAC7FDE924D6@gmx.de>
 <2DBEDC47-BD81-4121-B70D-B025828D1DD5@hibnet.org>
To: Ant Developers List <dev@ant.apache.org>
In-Reply-To: <2DBEDC47-BD81-4121-B70D-B025828D1DD5@hibnet.org>

--Apple-Mail=_1C95375E-E8AB-4A52-8BD1-48D748D68F2E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hello Nicolas,

unfortunately the status is 200 in BasicURLHandler checkStatus.

Looks like my proxy is not behaving in a standard, decent way.

My ISP is Verizon - it would be an uphill battle to make them change the =
behavior of the proxy.

Antoine

I have looked at the HTTP error status=20
On Jan 26, 2015, at 4:59 AM, Nicolas Lalev=E9e =
<nicolas.lalevee@hibnet.org> wrote:

>>=20
>> Le 26 janv. 2015 =E0 00:56, Antoine Levy Lambert <antoine@gmx.de> a =
=E9crit :
>>=20
>> Hi,
>>=20
>> when I run the ivy test suite on my computer at home, the =
iBiblioResolverTest.testErrorReport errors.
>>=20
>> The error happens on line 251 :
>>=20
>> ResolvedModuleRevision rmr =3D resolver.getDependency(new =
DefaultDependencyDescriptor(mrid,
>>               false), _data);
>>=20
>> What happens on that line is that :
>>=20
>> - the proxy that I use at home produces an HTML5 error report about =
the http://unknown.host.comx=20
>> - this error report is consumed by ivy as if it was a POM file and =
generates this exception :
>>=20
>> java.text.ParseException: Already seen doctype.
>> at =
org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.newParserExcept=
ion(PomModuleDescriptorParser.java:375)
>>=20
>> One workaround to deal with that is to surround the call to =
resolver.getDependency with try/catch and also to remove the last =
assertion :
>> assertLogContains("tried =
http://unknown.host.comx/org/apache/commons-fileupload/1.0/commons-fileupl=
oad-1.0.jar=94)
>>=20
>> This of course is a workaround.
>>=20
>> Is it also an intelligent solution ?=20
>>=20
>> Is the normal behavior when trying to access a non existent host name =
to get an UnknownHostException ?
>=20
> I don=92t know much about proxy, but considering the IP stack, I would =
understand that the IP is resolved, thus to be the IP of the proxy. But =
then I don=92t understand why Ivy is not properly failing. I would =
expect the proxy to at least return a 404. Could you confirm the HTTP =
status ? You can put a break point in BasicURLHandler#checkStatusCode.
>=20
> Nicolas
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org


--Apple-Mail=_1C95375E-E8AB-4A52-8BD1-48D748D68F2E--