Joshua,
That makes sense. Many thanks.
>> Trying to prove a caching-proxy configuration.
>
> From my understanding, CacheDefaultExpire is used *only* if neither an
> explicit expiry time nor a Last-Modified header are present in the
> response. Your responses have Last-Modified headers and ther
Trying to prove a caching-proxy configuration. With the server configured
as below cache headers are marked with the CacheMaxExpire value, not the
CacheDefaultExpire. I'm making requests for static content (a jpg file)
on the caching-proxy server. Meaning there is only my browser and the
server
It looks like I gave you bum info on the use of _default_. Doesn't look
like you can use it.
http://httpd.apache.org/docs/2.1/vhosts/name-based.html has all the right
answers.
> I read through the entire /etc/httpd/conf /httpd.conf and found no place
> to put the IP in. In the "windows" versio
Take a look at http://httpd.apache.org/docs/2.1/vhosts. Although this is
specific to Apache 2.1+, there are similar pages for each major version.
Find yours.
The lines you quoted originally actually had a couple of issues.
Specifically, in order to do name based virtual hosting you need this
di
Look for the NameVirtualHost directive, above where your VirtualHosts are
defined. It needs the IP address of the box. That's what the error
message below is telling you.
It's easy to misread this into thinking it's talking about the same
VirtualHost directives you quoted.
> Sep 27 12:56:28 mid
Clearly a developer question, but I'll ask here first since I'm not
subscribed elsewhere.
We are building a custom module to handle authentication for Apache and
need to configure some parameters for run time. Apache doesn't seem to
care for things it doesn't understand in httpd.conf upon startup
> This would probably be better on the [EMAIL PROTECTED] list.
Understood. I've looked at some of the bug reports and they are
considerably more detailed than what I have so far.
> Do you have the possibility to reproduce whatever is
> causing this on any other platform? I doubt unixware
> is a
First timer here. What can I do to isolate/document this further? I've
looked at the open bug reports and don't see anything that looks related.
Nothing in the error log.
Apache 2.1.7 (also checked 2.1.6, same prob)
UnixWare 7.1.3 MP2
Using Apache as a caching-proxy, nothing special about the c
