On 10/7/05, kloomis [EMAIL PROTECTED] wrote:
The most likely cause of this is that the cable modem is stripping (or
rewriting) the Host header and not simply forwarding packets. That
means that apache doesn't have the information to do name-based
virtual hosting. You can confirm that by
At 01:09 PM 10/7/2005 +0200, you wrote:
OK, now the initial page is opening
at the right directory, but all the
follow on links are reverting to only one directory. Could
this be an
Apache problem or is it my configs for the application I'm
using?
That will probably be the application. Often
On 10/7/05, kloomis [EMAIL PROTECTED] wrote:
At 01:09 PM 10/7/2005 +0200, you wrote:
OK, now the initial page is opening at the right directory, but all the
follow on links are reverting to only one directory. Could this be an
Apache problem or is it my configs for the application I'm
At 05:27 PM 10/7/2005 +0200, you wrote:
mod-rewrite does not touch anything going from
your server to your
client. If your clients get webpages with the wrong absolute url's
in
them, than this is because the webpages contain these absolute
URLs,
or the application generating the webpages
kloomis wrote:
Hello:
I'm having no luck with virtual hosts.
I have a domain name: myDomain.com and a sub-domain name: test.myDomain.com
I would like myDomain.com to go to /var/www/sites/prod and
test.myDomain.com to go to /var/www/sites/dev
My hosts file reads: 127.0.0.1 myDomain.com
At 03:33 PM 10/6/2005 -0700, you wrote:
kloomis wrote:
I'm having no luck with virtual hosts.
My hosts file reads: 127.0.0.1 myDomain.com localhost.localdomain
localhost asus
(do I need a test.myDomain.com in here?)
Yes I believe you do. Though it maybe should go through a DNS
server, but this
--- kloomis [EMAIL PROTECTED] wrote:
At 03:33 PM 10/6/2005 -0700, you wrote:
kloomis wrote:
I'm having no luck with virtual hosts.
My hosts file reads: 127.0.0.1 myDomain.com
localhost.localdomain
localhost asus
(do I need a test.myDomain.com in here?)
Yes I believe you do. Though
The most likely cause of this is
that the cable modem is stripping (or
rewriting) the Host header and not simply forwarding packets.
That
means that apache doesn't have the information to do name-based
virtual hosting. You can confirm that by logging the Host header
in
the access log
OK, now the
