URL rewrites - IBM Lotus Domino

pekka.panula at sofor.fi pekka.panula at sofor.fi
Tue May 18 09:50:21 MSD 2010

> You first need to understand how Domino is producing those URLs 
> before you can even think of doing a mapping in Nginx.
> Domino in general works with:
> * UNID (Universal ID. Should be unique in a Domino domain)
> * NoteID (should be unique per database)
> * Replication ID (should be unique per Domino domain)
> Domino has many ways to represent a URL for the same thing. For example:
> * http://www.isku.lt/IskuASP/interiorweb.nsf?OpenDataBase
> * http://www.isku.lt/IskuASP/interiorweb?OpenDataBase
> * http://www.isku.lt/IskuASP/<replication id>?OpenDataBase
> * http://www.isku.lt/<replication id>?OpenDataBase
> All the above could open the same database.
> Then after the database you can address many different things:
> <database>/<view|document|page|folder|outline|frameset|agent|
> webservice|xpages|image resource|file resource|Lotuscript library|
> Javascript library|etc>?<action>
> And most of those things after the database can be either a name 
> (like "sp" in your case) or a UNID or an alias or or or...
> You can off course write mappings for that. But your customer needs 
> to tell you what needs to be mapped to what. Your customer can 
> impossibly expect you to know all the combinations. He is the one 
> who needs to tell you what to do. After you have that list, writing 
> the rewrites in Nginx is easy.
> // Steve

In this case i dont need to map those different types but those i copied, 
they are actual URL that web site produces in certain situation, eg. link 
in the site that needs to go to new site. But as they are URL args in 
nature and contains special characters etc, like spaces, / or \ chars, 
etc. i wonder how in actually rewrite those URLs in nginx, its kinda 
difficult because most part of URL is arguments. 

   Pekka Panula, Sofor Oy - Jatkuvat palvelut
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20100518/579120c6/attachment.html>

More information about the nginx mailing list