|
Rich,
Glad to be of help for once.
Roger
On 12/15/2004 6:59 AM, Rich.Frye@xxxxxxxxx wrote:
Roger,
I appreciate the update and will take your advice on a static Web page. Hope you have a great holiday.
"Roger Vicker, CCP" <rv-lists@xxxxxxxxxx> Sent by: domino400-bounces+rich.frye=sch-i.com@xxxxxxxxxxxx
12/14/2004 10:13 PM
Please respond to
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
To Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx> cc
Subject Re: Hiding Lotus Domino Behind Apache Server
Rich,
With the Domino plugin in Apache any request for "Welcome" page (http://mydomain.com) will get the Apache served pages.
Only requests that the plugin recognizes as being for Domino (I think it must have a .nsf as in http://mydomain.com/xyz.nsf) will be requested from the Domino port and forwarded out as the response.
That is, Apache doesn't redirect, so you don't need to open the Domino port on your firewall. It just repeats the request to Domino and repeats the answer it gets to the client. Therefore, the only change your ISP would have to make is if the Apache is at a different IP address than the old one.
I think you will have to setup your homepage as a static page in Apache and have Domino pages as a link from there. I don't think you can have the "Welcome" page come from Domino via Apache unless something can be done with server side includes or something else special about the "Welcome" page that Apache serves.
A request that ends in "/", which just going to the domain implicitly does, has Apache look for files in the "document root" that match the files listed on the "Welcome Page" tab. If the URL looks more like a path with more "/"s then it uses them as sub folders in "document root" and looks for the same files. If "document root" = /www/server1 and "Welcome Page" = index.html then http://yourdomain.com/abc/xyz will look for /www/server1/abc/xyz/index.html
Now you can use other Apache directives to point URL paths to entirely different IFS folders, but that is for advanced Apache which I haven't really reached yet.
Roger
On 12/14/2004 12:11 PM, Rich.Frye@xxxxxxxxx wrote:
I can access my homepage if I type in my IP Address:81 from my internal network, pretty typical.
When I attempt to use port 80, I get the default Apache page.
My ISP points to my Web site on a server about to be replaced (once this is resolved) over port 80.
I thought that Apache would redirect incoming requests on port 80 for Domino to port 81. Don't know what I am missing?
"Roger Vicker, CCP" <rv-lists@xxxxxxxxxx> Sent by: domino400-bounces+rich.frye=sch-i.com@xxxxxxxxxxxx
12/13/2004 05:03 PM
Please respond to
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
To Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx> cc
Subject Re: Hiding Lotus Domino Behind Apache Server
Rich,
I did this at Domino 6.0.3 and OS/400 V5R1 and have upgraded to Domino 6.5.1 and OS/400 V5R2 (soon V5R3) so am close to your config.
The documents are fairly simple. Change the HTTP port in Domino, add the Domino plugin to Apache (you did mean the one on the iSeries...), tell it the port Domino is listening on, restart everything. There may have been an "Apache plugin" to add to Domino but it should also be in the documents. I don't really remember one just that the documentation was pretty straight forward and I was done in an hour.
Actually using it may take a little more. All we used it for was access to webmail via http://yourdomain.com/mail/usermailfile.nsf
Roger Vicker, CCP
On 12/13/2004 1:32 PM, Rich.Frye@xxxxxxxxx wrote:
I would like to hide my Domino 6.5.2 server behind my Apache 2 server. Anyone attempt before? I am running 5.3 on my iseries
-- *** Vicker Programming and Service *** Have bits will byte *** www.vicker.com *** Node: Was aware of. The past tense of "know."
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.