|
Sarah, Due to the current project plan, I can't combine all 3 now, right now... people use all 3 right now. That will happen later though. Right now, I just need to move them all to port 80. They are different applications on the same host... not 3 separate companies... so they will all be www.alfa.com. -Jeff
"Sarah Poger Gladstone" <listmember@xxxxxxxxxxxxxx> 11/27/2006
6:26:57 PM >>> Jeff- I would consolidate everything to 1 Apache instance. ( ie one httpd.conf file ) Have the following directives: # start name virtual hosts listen 80 NameVirtualHost *:80 <VirtualHost *:80> ServerName www.alfa.com </VirtualHost> <VirtualHost *:80> ServerName www.beta.com </VirtualHost> On 11/27/06, Jeff Day <Jeff.Day@xxxxxxxx> wrote:
Hi Matt, We don't use Websphere here. The original site here was built on
port
80. Then based on company needs, functionality was expanded and encompassed 2 other instances. What I need to do, is centralize everything back to http default port 80. So do you think the apache tags below will do what I need? Jeff<Matt.Haas@xxxxxxxxxxx> 11/27/2006 12:55:31 PM >>>When I'm doing virtual hosts, I have a VirtualHost container for
each
site but if the content is being served by something like WebSphere which has it's own plug in that handles the content, you don't need
to
even bother with virtual hosts (unless you want separate access and error logs for each virtual host). All you need to do is load the plug-ins and add Listen directives for each combination of IP
address
and port. Matt -----Original Message----- From: web400-bounces@xxxxxxxxxxxx
[mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Jeff Day Sent: Monday, November 27, 2006 12:23 PM To: web400@xxxxxxxxxxxx Subject: [WEB400] Virtual Host questions Hi, While I am new to virtual host entries, I've been reading a lot of material on it, and wanted to run a change I need to make by all of you, and see if I'm on track. I have 3 *HTTP instances running in QHTTPSVR. I need #2 and #3 instances to use port 80 as well, and it seems that a Name-Based Virtual Host is what I need. All 3 instances run fine on the ports they are currently configured on. All I want to do is change them to port
80.
Instance: #1. runs on port 80, and has been for years. #2. no static pages/content #3. portal software, has no static pages/content - dynamically
driven
by software If I add the following lines between # start and # end, to Instance
#2
and #3, should this work for my situation? # start name virtual hosts # external IP NameVirtualHost 111.111.111.111:80 # internal IP NameVirtualHost 192.168.1.111:80 <VirtualHost 192.168.1.111:80 111.111.111.111:80> ServerName www.alfa.com </VirtualHost> # end Is there a recommended spot in the configuration file to place these lines? After or before anything? Is there anything that is required that I'm missing? Do I need to remove the Listen command from the 2 instances I
change?
If I leave the Listen command, will it serve content over both
ports?
Do I need to include the port numbers with the IP addresses on the VirtualHost tag? Thank you and Best Regards, Jeff
************************************************************************
********************** If the reader of this email is not the intended recipient(s), please be advised that any dissemination, distribution or copying of this information is strictly prohibited. Johnson Matthey PLC has its main place of business at 2-4 Cockspur Street, London (020 7269 8400). Whilst Johnson Matthey aims to keep its network free from viruses you
should
note that we are unable to scan certain emails, particularly if any part is encrypted or password-protected, and accordingly you are strongly advised to check this email and any attachments for viruses. The company shall NOT ACCEPT any liability with regard to computer viruses transferred by way of email. Please note that your communication may be monitored in accordance with Johnson Matthey internal policy documentation.
************************************************************************
********************** This message has been scanned for viruses by MailControl - www.mailcontrol.com -- This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400. -- This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400. This message has been scanned for viruses by MailControl - www.mailcontrol.com Click https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg== to report this email as spam -- This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.
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.
midrange.com
