-
Suggestion
-
Resolution: Fixed
-
None
-
Standalone, Windows Server 2003. JDK 1.4.
We just acquired a full license of Confluence, partly in order to use as a portal for each department, with links to the various resources and knowledge sources we already have in place. Being to link to them is therefore of critical importance. Most of these sources are for better or for worse in Lotus Notes databases. Unfortunately it seems Confluence doesn't currently support the notes:// protocol in links. It does not convert such links to a hyperlink and instead highlights them as errors.
Please could we add notes:// to the list of protocols understood? There are loads of others that might be useful; I'm not sure if they're included at the moment. e.g.
notes://
ftp://
etc...
This looks very similar to issue JRA-2096, which has been resolved almost two years ago, in the oscore library. To quote Charles Miller, "Unfortunately, we couldn't use the oscore URL-locating code in Confluence, as it was incompatible with all the other stuff that needed to be done during the page->wiki conversion."
- is related to
-
- Closed
- relates to
-
CONFSERVER-13451 XSS bug in wiki markup link rendering
-
- Closed
-
[CONFSERVER-3086] Hyperlink other protocols (e.g. notes://) automatically
Look at UrlUtils from oscore - it contains a java implementation of the URL spec. If you develop regexps - can you donate them back to that code?
Give me a yell if you would like me to show you how it can be used.
Mike Cannon-Brookes
added a comment - We seem to be getting more and more requests for this. Let's make it editable as a configuration setting for 1.5.
To do this, I think we'd need to make the UrlRendererComponent configure itself with a list of protocols from an application config setting, and store those regexes (currently static). Shouldn't be too difficult a change.
Currently supported: http://, https://, ftp://, ftps://, 
, nntp://, news://, irc://, file:
Often requested: notes://, ssh://, telnet://.
I'd remove ftps://, nttp://, news:// and irc:// from the default - surely not very well used.
m
Mike Cannon-Brookes
added a comment - We seem to be getting more and more requests for this. Let's make it editable as a configuration setting for 1.5.
To do this, I think we'd need to make the UrlRendererComponent configure itself with a list of protocols from an application config setting, and store those regexes (currently static). Shouldn't be too difficult a change.
Currently supported: http:// , https:// , ftp:// , ftps:// , , nntp:// , news:// , irc:// , file:
Often requested: notes://, ssh://, telnet://.
I'd remove ftps:// , nttp://, news:// and irc:// from the default - surely not very well used.
m 
Andrew Ostler
added a comment - I'd like to add ums:// to this list.
Or make the list of protocols a server-side config setting.
cheers,
os.
Andrew Ostler
added a comment - I'd like to add ums:// to this list.
Or make the list of protocols a server-side config setting.
cheers,
os. Thank you for the improvement suggestion. It is to late in the release cycle to be implemented for 1.4, but we will consider it for the next release planning.
cheers,
Jens
Hi,
This has been completed in CVS. On the advice of Scott, we have changed the Link resolver to check against UrlUtils in OSCore, instead of the hard-coded protocols list currently in the renderer. As a result, a link with any protocol can now be rendered(and automatically hyperlinked) when surrounded by square brackets (as you would with any other link).