I'd call it a bug Conor
> -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 2 January 2002 11:52 AM > To: ant-dev > Subject: Bug in get task? > > > > I am updating get.html with the uname/pass stuff; doing a code > walkthough in > the process, where I came across this little problem: > > What happens in <get> if one of username or password is not set, > but not the > other? On line 138 the code goes > > if (uname != null || pword != null) { > String up = uname + ":" + pword; > ... > } > Which seems to me that it will concate a null into the authentication > string. This is not normally considered a good thing. Bug? Or > some aspect of > RFC 2517 or whatever that I have missed? > > -Steve > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
