Support for ldap_2.servers.name.customDisplayUrl (like with Netscape 4.5)

UNCONFIRMED
Unassigned

Status

--
enhancement
UNCONFIRMED
10 years ago
10 years ago

People

(Reporter: michael, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9

In former times Netscape Communicator 4.5 supported a preference which allowed to let the user double-click on a LDAP entry found in the address book and then open a (HTTP-)URL based on the DN to be opened by the browser. I happily used this to directly jump to editing this entry with web2ldap.

This was very handy but does not seem to be supported anymore. :-(

Unfortunately the old docs are gone (former location was http://developer.netscape.com/docs/manuals/communicator/ldap45.htm#improved-html-display just in case somebody has a copy of that).

I have an web2ldap FAQ entry regarding this here: http://www.web2ldap.de/faq.html

I'd be glad if this feature would be reimplemented. Preferrably by merging the complete LDAP URL describing this entry with the URL defined in customDisplayUrl.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
(Reporter)

Comment 1

10 years ago
Wading through LDAP-related bugs this enhancement also might be related to the stuff around network.protocol-handler.*

So how about defining something like:
user_pref("network.protocol-handler.rewriteurl.ldap", "http://localhost:1760/web2ldap?%u")

There are similar feature requests for chasing ISBN numbers etc.
Bug 269917 – Support for ISBN URN Scheme (RFC3187)

Also integrating web2ldap (or another web-based LDAP client) is an elegant work-around for these feature requests:
Bug 86405 – Make LDAP addressbooks editable
Component: Address Book → MailNews: Address Book
Product: Mozilla Application Suite → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.