140851 - LDAP query in browser loads entries into address book instead of query results like Netscape 4.x

Status: RESOLVED EXPIRED

(SeaMonkey :: Location Bar, enhancement)

Description

[[e-mail]]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0+)
Gecko/20020428
BuildID:    2002042808

An LDAP query entered as a URL in the browser loads into the address book. This
means you can't see the real LDAP entry/attributes names/values
Netscape 4 showed results to browser
It should be an option to have results to browser or address book.

Reproducible: Always
Steps to Reproduce:
1. ldap://server/base??sub?


Actual Results:  Address book fires up and results loaded into that

Expected Results:  loaded all LDAP query results into the browser like netscape
4 does
an option to go to address or browser window would be ok

Comment 1

[Hugo Kortschak]

I support this request. Many enterprises host data of various things in LDAP
based directory servers (e. g. inventory of applications). The redirection of
the LDAP output into the address book might be good enough for
'consumer-editions' but is not flexible enough for entreprise capability. 
The least solution should be an option to redirect all output into the browser's
window.

Comment 2

[Niranjani Raya]

Can we have an update on this bug?

Comment 3

[[e-mail]]

What kind of update? From who?

Comment 4

[Philip Peake]

I also would like the ability to use the browser to view arbitrary LDAP data via
an LDAP URL as is possible with Netscape 4.x.

The ability to define which behaviour you want via some configuration setting
would be optimal. If this is not possible, then simply viewing the LDAP data as
in Netscape 4.x would be preferred over the current behaviour.

I consider the current behaviour to be a bug, since an LDAP URL is defined to
return the LDAP data, not fire up some other application to display it in a
fixed form. I would encourage the original submitter (Matthew) to re-classify
this as a P3 bug with severity normal.

Comment 5

[[e-mail]]

Not sure if this is valid as a bug. Can we get a comment from some mozilla people?

Comment 6

[Philip Peake]

Matthew, there is no defined behavior for dealing with data returned by an ldap
URL, so whether this is a bug or not really depends upon concensus. I contend
that  this is a bug based upon the fact that an ldap url can access arbitrary
data, trying to force arbitrary data into an address book entry is obviously not
the right answer. It is a bug because it prevents Mozilla from replacing
outdated Netscape Communicator in many enterprises which depend upon the ldap
url being able to display arbitrary data.

I would be more than happy if there was a configuration option to either display
the raw data (as in Netscape Communicator), or to attempt to display the data in
address book format - then the choice is up to the user and both camps (Netscape
vs IE behavior) will be happy.

Comment 7

[Greg Ubben]

FWIW, see bug 114097 for a Unix work-around using an external handler.
(I'm not reading mail, BTW...)

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Philip Peake]

Mozilla 3.0.11

Behavior is marginally better.

When opening an LDAP URL the user is prompted to select address book or "another application".

There is, of course, no really appropriate "other application".
What is required is the same behavior as the old Netscape browser had - which is to format and display the result *in the browser*.

Comment 10

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420