Re: URI class with userinfo ?
When you want specified-protocol-featured URI specification, Please refer and try the URI extended classes like HttpURL, not URI. Sung-Gu P.S.: as you guys know, URI is for the very basic general use. - Original Message - From: "Adrian Sutton" <[EMAIL PROTECTED]> > > So should we definitely should never use the credentials from the URI > but we could add a method that allows you to get them back out if > required. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: URI class with userinfo ?
My understanding is that HTTP URLs do not include user info and thus that data should be stripped (or probably an exception should be thrown if we're being strict about it). FTP URLs on the other hand do. Having said that, there's no harm in preserving the user credentials so that they can be returned by the URI class, but it would be messy to try and actually use the credentials from the URL in HttpClient for authentication. From RFC 2616: http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]] So should we definitely should never use the credentials from the URI but we could add a method that allows you to get them back out if required. Regards, Adrian Sutton. On Friday, July 11, 2003, at 02:58 AM, Oleg Kalnichevski wrote: Why is this the case? I have no idea. Anyone else has some thoughts on this one? Sung-Gu, maybe? Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: URI class with userinfo ?
> Why is this the case? I have no idea. Anyone else has some thoughts on > this one? > Sung-Gu, maybe? Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: URI class with userinfo ?
Yes, it seems that none of the methods for getting the full URI include
the userinfo. It is intenionaly removed in setURI():
if (_authority != null) { // has_authority
if (_userinfo != null) { // by default, remove userinfo part
if (_host != null) {
buf.append(_host);
if (_port != -1) {
buf.append(':');
buf.append(_port);
}
}
} else {
buf.append(_authority);
}
}
Why is this the case? I have no idea. Anyone else has some thoughts on
this one?
The only workaround at this point is to build the URI string manually
from all of the constituent pieces, much like setURI() does.
Mike
Marcus Crafter wrote:
Hi All,
Hope all is well!
If I put the following text into the URI class:
ftp://anonymous:[EMAIL PROTECTED]/incoming/
Is it possible to get that text back out of the URI class via one of the
get* methods, or similar ?
From what I can see, all return the URI excluding the user info, but I need
in my application I need to get the original string back to pass to the
Avalon SourceResolver library.
I guess there must be some way to extract the original string ? Have I missed
something somewhere ?
Cheers,
Marcus
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
URI class with userinfo ?
Hi All, Hope all is well! If I put the following text into the URI class: ftp://anonymous:[EMAIL PROTECTED]/incoming/ Is it possible to get that text back out of the URI class via one of the get* methods, or similar ? >From what I can see, all return the URI excluding the user info, but I need in my application I need to get the original string back to pass to the Avalon SourceResolver library. I guess there must be some way to extract the original string ? Have I missed something somewhere ? Cheers, Marcus -- . ,,$, Marcus Crafter ;$' ':Computer Systems Engineer $: : ManageSoft GmbH $ o_)$$$: 82-84 Mainzer Landstrasse ;$,_/\ &&:' 60327 Frankfurt Germany ' /( &&& \_' . &&&: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
