I have a link in this format:
http://user:[email protected]
How to get user and pass from this URL?
-
5What have you actually tried? What was the expected result? If you didn't get the result you expected, what did you actually get? Sorry, this is not a "give me teh codez" site - please read the FAQ if that is unclear.Brian Driscoll– Brian Driscoll2012-02-22 19:34:05 +00:00Commented Feb 22, 2012 at 19:34
-
3From the FAQ: "You should only ask practical, answerable questions based on actual problems that you face." and "We’re all here to learn together. Be tolerant of others who may not know everything you know."Peter Hedberg– Peter Hedberg2012-10-25 17:48:34 +00:00Commented Oct 25, 2012 at 17:48
-
Better question is how to remove it :PJay– Jay2015-01-10 06:23:44 +00:00Commented Jan 10, 2015 at 6:23
Add a comment
|
2 Answers
Uri class has a UserInfo attribute.
Uri uriAddress = new Uri ("http://user:[email protected]/index.htm ");
Console.WriteLine(uriAddress.UserInfo);
The value returned by this property is usually in the format "userName:password".
http://msdn.microsoft.com/en-us/library/system.uri.userinfo.aspx
3 Comments
Kenneth LeFebvre
This only works if there is NOT an "@" symbol in the credentials (common for usernames that are email addresses, or in strong passwords).
supertopi
True. Note that '@' is a reserved character in the Uniform Resource Identifier, specified by the RFC. See tools.ietf.org/html/rfc3986#page-12 As you can see there are a lot of characters, when contained in a username or a password that make the URI invalid.
Kenneth LeFebvre
Yeah, when we did this, we ended up parsing out the credentials and using HttpUtility.UrlEncode on them before adding them back. Windows Explorer will accept un-encoded credentials (which is where our users are copying/pasting them into our app). Also, UriBuilder does not encode them when it builds the URI. I would expect a "builder" to handle things like that; it's annoying to have to parse stuff before passing it off to a parser. :)
I took this a little farther and wrote some URI extensions to split username and password. Wanted to share my solution.
public static class UriExtensions
{
public static string GetUsername(this Uri uri)
{
if (uri == null || string.IsNullOrWhiteSpace(uri.UserInfo))
return string.Empty;
var items = uri.UserInfo.Split(new[] { ':' });
return items.Length > 0 ? items[0] : string.Empty;
}
public static string GetPassword(this Uri uri)
{
if (uri == null || string.IsNullOrWhiteSpace(uri.UserInfo))
return string.Empty;
var items = uri.UserInfo.Split(new[] { ':' });
return items.Length > 1 ? items[1] : string.Empty;
}
}
2 Comments
Jay
Missed@ domain parsing
Hiep
We often need both at the same time gist.github.com/duongphuhiep/13f104e4229bf7e1869921e034834ec6