Closed Bug 198463 Opened 21 years ago Closed 20 years ago

URLs are wrongly displayed in message and cannot be opened by clicking

Categories

(MailNews Core :: MIME, defect)

x86
Windows NT
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: wzeikat, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312 (installed from talkback zip)

our request tracker software sends with ticket summaries and URLs where the
request tracker host's browser interface can be accessed directly.

some of the URLs arrive in the form (copied from mail message source):

X-Mailer: Perl5 Mail::Internet v1.53
Precedence: bulk
Managed-BY: RT 2.0.14 (http://bestpractical.com/rt/)
RT-Ticket: rt-system.desy.de #26000
RT-Originator: zeikatw@mail.desy.de
X-RT-Loop-Prevention: rt-system.desy.de
Content-Type: text/plain; charset="iso-8859-1"
Content-Length: 759


<URL https://rt-system.desy.de/Ticket/Display.html?id=26000 >

(end of copy from message source)
the line
"<URL https://rt-system.desy.de/Ticket/Display.html?id=26000 >" is being
displayed totally underlined, just like other URLs.

"Copy link location" gives out the following:
URLhttps://rt-system.desy.de/Ticket/Display.html?id=26000
and that can of course not be opened in the browser, so clicking on that link
results in an error message "urlhttps is not a registered protocol".




Reproducible: Always

Steps to Reproduce:
1. view the message
2. click on the link


Actual Results:  
error message "urlhttps is not a registered protocol"

Expected Results:  
opened the URL in a browser window

We have been testing mozilla 1.2.1 as one of the netinstall supported browsers
in our IT environment and were about to release it for all users when 1.3 final
was released. 1.3's promising new features get spoiled by this effect (at least
for me, the other software developers here will still need to test/confirm my
observations).
The same email is displayed correctly in 1.2.1 - and the URL is opening without
problem.
=>WFM per reporter's comment 1.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.