Domino – Redirect Rules and Strict Redirect URLs


This one was a bit of a challenge until I finally found a solution – after HOURS of work.

 

My Scenario:

I have a Domino URL that gets generated with a query at the end and I can’t change that. I need to redirect that URL to another strict/defined URL on another system that will not work with a query added to the end of the incoming URL – here an (obfuscated) example:

Original Domino URL: https://www.mydomain.com/something/anyDB.nsf?addAnotherQuery
URL To redirect to: https://www.anewdmain.com/something/anyUrlHere

If you just use a standard redirect rule (either standalone or for Internet sites) the query [?addAnotherQuery] will be appended to the redirect URL resulting in this example:

https://www.anewdmain.com/something/anyUrlHere?addAnotherQuery

Solution

In my case this was a problem as the FW was blocking unknown URLs and would not let anything non-defined through. I tried everything – all sort of combinations of redirects to redirect to another redirect,  to substitution rules… the query was always appended to the end of the resulting URL and the FW was rejecting me. I even redirected to an IBM HTTP server to use the rewrite capability – which is when I had  an epiphany after 8 hours of straight work: In Apache, when doing a re-write,  you can add a [?] to the end of the rewrite and it will cause any queries to be stripped from the resulting URL. I jut thought … let’s give it a try and …. it worked!

Here an screenshot of the example:

The redirector rule is otherwise standard. You can match any incoming URL patters using asterisks etc. or point it to other redirector results. You can also point to a local URLs by changing the [Redirect to this URL] to string that the Domino server will resolve locally such as [/anyfolder/adifferentDB.nsf?] or a URL created by another redirector such as [/NewSiteHere/Results?] – and by adding the [?] in the end any query like function (i.e. the very common query [?Open] appended to the end of a dB in a URL] will be stripped from the resulting URL.

Advertisements

Open Mic Webcast: Troubleshooting Duplicate Mail Messages in IBM Notes – 24 July 2013


Looks like a good webcast again. I often get duplicate mail messages and it drives me nuts …. I will likely listne in to this one.

 

 

 

You are invited to join an Open Mic Webcast on the topic “Troubleshooting Duplicate Mail Messages in IBM Notes.” This event will be held Wednesday, 24 July 2013 at 11:00 AM EDT (15:00 UTC, or GMT -4), for 60 minutes. After a presentation, you will have the opportunity to ask questions directly of IBM Developers and Support Engineers. See more details below. (Note: To view this information online, go to http://www.ibm.com/support/docview.wss?uid=swg27038764

When Date: 24 July 2013
Time: 11:00 AM EDT (15:00 UTC, or GMT -4), for 60 minutes
Bookmark Webcast Technote
# 7038764
Title: Open Mic Webcast: Troubleshooting Duplicate Mail Messages in IBM Notes – 24 July 2013
Doc #: 7038764
URL: http://www.ibm.com/support/docview.wss?uid=swg27038764Before the call, the technote will include:

  • An iCal attachment to add this event to your calendar
  • Details on how to join the call and web conference
  • The slides that will be presented during the session

A couple of weeks after the call, the technote will be updated to include:

  • A recording of the session
  • A written Q&A transcript

To be notified when the Webcast technote is updated, subscribe to IBM My Notifications and select “Webcasts” as a document type of interest.

IBM SmartCloud Meeting (web conference) URL https://apps.na.collabserv.com/meetings/join?id=9526-3802
Web conference password: webcast
Dial-in Information Dial-in Passcode: 6939689US/Canada phone numbers:
Toll-free number (866) 803-2145
Toll number (210) 795-1099

International phone numbers

ndinfo with “unsubscribe” in the subject line. Please be aware that doing so will also unsubscribe you from periodic Support Content Highlights newsletters. If you know of others who wish to subscribe, have them send a message to ndinfo with “subscribe” in the subject line.

This e-mail was sent to the following e-mail address: victor