Hi!
The patch sounds great! :)
Armando
-Original Message-
From: Michael Becke [mailto:[EMAIL PROTECTED]
Sent: jueves, 13 de marzo de 2003 2:50
To: Commons HttpClient Project
Subject: Re: Bug #12798: Feedback would be welcome
Functionality-wise it looks good. I think it only needs some
mentioned that
"Once a Contributor is nominated, all of the Committers for a subproject
will vote." (see http://jakarta.apache.org/site/roles.html)
Contributors' votes do not count unfortunately. But of course it's nice
to see what everybody thinks.
Arman
+1
-Original Message-
From: Jeffrey Dever [mailto:[EMAIL PROTECTED]]
Sent: miércoles, 19 de febrero de 2003 18:28
To: Commons HttpClient Project
Subject: [VOTE] nominate Michael Becke as a committer
Mike Becke has been an active contributor for many months. He has
worked on a diverse r
i would like to help in this new package :)
and it sounds great!
Armando
-Original Message-
From: Jeffrey Dever [mailto:[EMAIL PROTECTED]]
Sent: viernes, 07 de febrero de 2003 18:41
To: Commons HttpClient Project
Subject: Propose a new commons-uri package
This is just a draft regardi
can i vote? :)
> checkstyle.maxlinelen=100
+1
> checkstyle.pattern.publicmember=^[a-z][a-zA-Z0-9]*$
+1
> checkstyle.pattern.package=^[a-z]+(\.[a-z]*)*$
+1
> checkstyle.header.file=license.regexp
> checkstyle.header.regexp=true
+1
> checkstyle.ignore.maxlinelen=Header:
+1
> checkstyle.tab.width=4
+
i think that the problem #2 tipically exists when someone writes too many ".."
expressions without safety and then the idea of compensating author errors sounds fine
for me (but it is just an idea)
in the current code if the base uri is http://a/b/c/d;p?q and the relative uri is
../../../g then
Armando
-Original Message-
From: Mike Moran [mailto:[EMAIL PROTECTED]]
Sent: martes, 28 de enero de 2003 11:36
To: Commons HttpClient Project
Subject: Re: [PATCH] relative URIs - take 2
Armando Anton wrote:
>Hi!
>
>I was working in uri test cases too so i send some more case
Hi!
I was working in uri test cases too so i send some more cases testing abnormal
examples (you can find them in the RFC) :)
Most of the abnormal examples works well except two of them:
1. when the relative uri is empty > an exception is thrown (i think it is a good idea
to avoid empty uris)
