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 config. I am
>> p
I apologize for my lack of understanding. Next time I will give version and
platform along with the full configuration in the future. To answer you
question about the Weblogic stuff. The mod_wl_22.so file came from my
Weblogic installation. It is there proxy file. Also the Location
informatio
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 probably did
not do some things correctly, but it is working good for except for this one
thing that has just come up.
No problem. This forum i
Forgot to mention we are running 2.2.9 on Windows 2003. We are also behind a
load balance switch. So, technically users come in https and the lb switch
drops it down to the server running http port 8081.
John
awarnier wrote:
>
> What version of Apache are you using, on which platform ?
> Can
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 probably did
not do some things correctly, but it is working good for except for this one
thing that has just come up.
ServerRoot "C:/Program Files/Apache Softwa
What version of Apache are you using, on which platform ?
Can you give us you whole configuration file ? What you are telling us
about your configuration, and the URLs which you mentioned in your first
post, do not match.
About this :
Are you sure that you are really using name-based virtual h
How do I check to see if it is inheriting. Also, I tried adding the
DirectoryIndex in the VirtualHost section, but it still did not work.
John
awarnier wrote:
>
> With the configuration structure show below, your DirectoryIndex
> statement does not apply to the VirtualHost section. It appl
With the configuration structure show below, your DirectoryIndex
statement does not apply to the VirtualHost section. It applies to the
"main" configuration. When you use name-based VirtualHost sections,
whetever is outside of them normally only specifies defaults, overridden
(or not) by the
Here is the some of the information from my conf file.
ServerAdmin ad...@localhost
DocumentRoot "D:/docs"
ServerName x.x.x.x:8081
ServerAlias x.x.x.x:8081
ErrorLog "logs/partners3/error.log"
CustomLog "logs/partners3/access.log" common
SetEnvIf Remote_Addr "x\.x\.x\.x
But there is an index.html file in that directory. If I go to
/tpg/docfiles/online/index.html it works just fine. It is only when we try
to just hit a directory. It happens on any subdirectory after the root.
Hitting the root without a filename works fine. It finds the index.html and
load up.
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.
I think if this were the case they would get 403, or if Options Indexes is
enabled, the listing of the files in the directory.
On Thu, Oct 8, 2009 at 5:58
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://ww
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
13 matches
Mail list logo
