In fact I pretty much went with defaults on where everything was located in
the configuration file. So, the VirtualHost information was where it was
located to begin with.
John
awarnier wrote:
>
> jwberger wrote:
>> I completely agree that it is most likely an issue with my c
, /Softwaredownloads and /focis to none
on the SetHandlers, do you think that might fix it?
John
awarnier wrote:
>
> jwberger wrote:
>> I completely agree that it is most likely an issue with my config. I am
>> pretty new to Apache. Below is the complete config. I know I probabl
e problem in all likelihood is not with
> Apache, but with something in your configuration which prevents it from
> working. But the information you provide seems incomplete or
> inaccurate, so it is difficult to help you.
>
>
> jwberger wrote:
>> How do I check to see if it is
if you really know what you are doing.
> What do your "Listen" and "NameVirtualHost" directives look like ?
>
> The reason for all the questions and remarks above is : under Apache
> 2.x, there are hundreds or thousands of systems where the DirectoryIndex
> works exa
ally "inherited" by VirtualHost
> sections. You should check if this one is.
>
>
>
> jwberger wrote:
>
>> Here is the some of the information from my conf file.
>>
>>
>> ServerAdmin ad...@localhost
>> DocumentRoot "D:/docs&q
> the other folders you try to access.
>
> On Thu, Oct 8, 2009 at 5:58 AM, jwberger wrote:
>
>>
>> I am having an issue with the DirectoryIndex. We have it set as
>> DirectoryIndex index.html We have a site the runs at
>> https://www.site.com
>> .
>> Whe
. None of the subdirectories work.
John
Igor Cicimov wrote:
>
> 404 means "file not found" which means you don't have any index.html file
> in
> the other folders you try to access.
>
> On Thu, Oct 8, 2009 at 5:58 AM, jwberger wrote:
>
>>
>>
I am having an issue with the DirectoryIndex. We have it set as
DirectoryIndex index.html We have a site the runs at https://www.site.com.
When we hit that site as shown it comes up fine because there is an
index.html file there. However, if we go further down to
http://www.site.com/tpg or http
Jay,
That is not the problem I am having. All of our DMZ sites sit behind a Load
Balance switch and all run on port 8080. Our public facing domain names\IP
addresses (Public URL's) are housed on the Load Balance switch and run on
port 80. When someone hits our Public url, they hit the LB switc
me up. I reversed
to shut the down on at a time and each time the site would longer be
available. I no longer have a site or config that has Listen 8080.
John
William A. Rowe, Jr. wrote:
>
> jwberger wrote:
>> I did that but it still seemed like if I had only one windows service
configured in
the conf file ran. Now I can create two new Windows services for the other
IP's and run them separately.
John
William A. Rowe, Jr. wrote:
>
> jwberger wrote:
>> I am novice when it comes to Apache. I have installed 2.2.9 on a Windows
>> 2003 server and can ge
could
get to all three IP addresses at port 8080. Again, maybe I am doing
something wrong.
John
William A. Rowe, Jr. wrote:
>
> jwberger wrote:
>> I am novice when it comes to Apache. I have installed 2.2.9 on a Windows
>> 2003 server and can get it to run fine. The serve
o your real server, and do a quick
> restart. It only takes a few seconds for the apache server to restart:
> is that too long to keep all your sites down?
>
> -Brian
>
> On Tue, Sep 30, 2008 at 3:55 PM, jwberger <[EMAIL PROTECTED]> wrote:
>>
>> They are bo
k connection to a specific
> process.
>
> But it sounds like virtual hosts might be sufficient for what you
> need. You don't actually need different apache services to run
> different sites at the same time.
>
> Hope that helps.
> -Brian
>
> On Tue, Sep 30, 200
I am novice when it comes to Apache. I have installed 2.2.9 on a Windows
2003 server and can get it to run fine. The server has one NIC with three
IP addresses bound to it. In installed Apache as a Windows service and
edited the httpd.conf file so that the server listened on port 8080. I
would
15 matches
Mail list logo
