IIRF ProxyPass & Domino OpenAgent

Topics: Developer Forum, User Forum
Nov 17, 2011 at 12:09 PM


We have a server with IIS 6.0 and Lotus Domino 8.5.2 runnig on port 8080. The goal was to delete the port of Domino in the Url and delegate the requests control to IIS, so we installed IIRF 2.1 and we configured it as ProxyPass.

But we have some problems with the pages that use Domino OpenAgent, we get an error code 404. We think that is caused because it losts server parameters. Is there possible?

Our ProxyPass configuration:

RewriteCond   %{HTTP_HOST} ^(domain\.com)$ [OR]
RewriteCond   %{HTTP_HOST} ^(www\.domain\.com)$

ProxyPass        ^/(.*\.nsf/.*)$  http://www.domain.com:8080/$1
ProxyPassReverse ^/(.*\.nsf/.*)$  http://www.domain.com:8080/$1

Are there any aditional parameters that we must bear in mind?


Nov 17, 2011 at 9:56 PM
Edited Nov 17, 2011 at 9:57 PM

IIRF should be able to do what you envision.

With the information you've provided to me, it's impossible to know the reason for the 404. The best way to diagnose the issue is to look in the IIRF log file for the diagnostic log statements associated to the particular request.

To do that you should set the IIRF LogLevel to 4 , then run one request, then examine the IIRF log. If IIRF handles the request, the log will indicate why the 404 was returned.

In some cases IIRF has not been properly configured and the 404 is returned directly from IIS to the requesting browser.  In other words, IIRF never "sees" the request.  In that case you need to do further verification of the initial IIRF configuration.  To do that you should start with the /iirfstatus request, and follow along with the directions in the IIRF documentation in the section entitled, "Verifying and Troubleshooting IIRF configuration".


Nov 18, 2011 at 9:17 AM

We checked IIRF logs and it seems thats works fine.

Searching the possible cause of the problem, we noticed that our code was checking the name and port of the request to generate the Url, and that was causing the error, because it goes to an inexistent Url.

Thank you for your response.