DotNet and Http Outlook Express question

  • Thread starter Thread starter Jason Huang
  • Start date Start date
J

Jason Huang

Hi,

In my ViaualC# .Net 1.1 windows form application, I have a string as:
http://MyIP/frmTestForm.aspx?lblTestNo=J2vTuX8Tv7qBn7HzK7O67XCdMQ==

On the MS Development Environment 2003
http://MyIP/frmTestForm.aspx?lblTestNo=J2vTuX8TvqBnHzKO6XCdM==,
the "==" and the
http://MyIP/frmTestForm.aspx?lblTestNo=J2vTuX8TvqBnHzKO6XCdM appears as a
hyperlink.
However, In the Outlook Express, the "==" looks just plain text and not in
the hyperlink.
I am not sure why exists this odd phenomenon.
Thanks for help.

Jason
 
In my ViaualC# .Net 1.1 windows form application, I have a string as:
http://MyIP/frmTestForm.aspx?lblTestNo=J2vTuX8Tv7qBn7HzK7O67XCdMQ==

On the MS Development Environment 2003
http://MyIP/frmTestForm.aspx?lblTestNo=J2vTuX8TvqBnHzKO6XCdM==, the "=="
and the
http://MyIP/frmTestForm.aspx?lblTestNo=J2vTuX8TvqBnHzKO6XCdM appearsas
a hyperlink.
However, In the Outlook Express, the "==" looks just plain text and not
in
the hyperlink.
I am not sure why exists this odd phenomenon.
Click to expand...

I'm sure it's just because OE has do make some assumptions in order to
extract the URL from the surrounding text, and in this case it made the
wrong one. Note that it can't just assume the URL will be terminated by
white space, because there may be other situations in which the URL is
terminated by something else (like a period, or parenthesis or something
like that).

Without explicit delimiters for the URL, there will always be ambiguity
when inferring implicit delimiters.

If you are writing code that emits a URL that you intend to be consumed by
a text-based display, rather than HTML where you can specify an <a> tag
for the URL, then you should put angle brackets around the URL. For
example:
"<http://MyIP/frmTestForm.aspx?lblTestNo=J2vTuX8Tv7qBn7HzK7O67XCdMQ==>".
In almost all of the applications I use regularly, this format is
recognized as delimiting the URL. It does confuse Mac Mail if it occurs
in quoted text, but frankly that's a bug in Mac Mail and not something you
should probably worry much about. :)

Pete
 
Back
Top