#2 FP only allows access to the ServerName in Apache?
I run a few shared webservers and we offer FrontPage
2002 to our customers. I've encountered a problem that
I'm unable to figure out a patch for, so I'm hoping that
people can 1) confirm this problem, and/or 2) tell me
how I can fix it, or point me in the right direction for
writing a patch.
The problem is that from what I can tell, you can
*ONLY* access domains set up for FrontPage via the
ServerName set up in Apache - if you try to access it via
IP or any other hostname/domain name, it errors out
saying it can't find the (system default) "we:80.cnf" file
(I don't have a default root web configured, which is why
this error shows up).
I am assuming that somewhere in this module, when it
receives a request, it's not able to figure out what
VirtualHost should handle the request - maybe because
this module traps the request before it even gets there?
This causes a problem because people should be able to
connect with FP via an IP or any other hostname that
resolves to the IP configured for the VirtualHost - if they
can't they have to make sure DNS is pointing to the
server before they can upload their site (real bad if
people want to move a site and check it before making it
active by switching DNS for their domain name).
I checked everywhere in the mod_frontpage.c and
couldn't find out where all the magic happens for
determining what the server name for the request is.
Can anyone help?
Logged In: YES
user_id=314984
I think teh problem you describe is an apache one and has
nothing to do with fp.
Easy workaround, btw, is to use a temporary subdomain/other
domain for testing if people switch their site.
Logged In: YES
user_id=314984
I think teh problem you describe is an apache one and has
nothing to do with fp.
Easy workaround, btw, is to use a temporary subdomain/other
domain for testing if people switch their site.
Logged In: YES
user_id=314984
I think teh problem you describe is an apache one and has
nothing to do with fp.
Easy workaround, btw, is to use a temporary subdomain/other
domain for testing if people switch their site.
Logged In: YES
user_id=616372
Actually it really does appear to be in the mod_frontpage
module, as I know this doesn't affect the RTR version of the
module for FP2000.
I was able to get a partial solution to this thouhg, so that at
least FP extensions on the site work via all URLs. I have
UseCanonicalName Off in my main httpd.conf, and then for
each VirtualHost, I have UseCanonicalName On. It doesn't re-
write the URL externally like I thought it would (and as a global
setting it appears to) - it just re-writes it internally so that all CGI
requests appear to be from the ServerName.
However, from what I've been told, when publishing using
FP2002, you still *have* to use the ServerName in the URL, ie
publish to http://domain.com/, where "domain.com" is the
ServerName value in the VirtualHost config file.
I tried to fiddle with some of the stuff in the mod_frontpage.c
module, however my Apache API knowledge is practically nil so
I didn't fair too well. I do believe though, that mod_frontpage.c
is grabbing the domain name from the URL in the request and
using that to attempt to determine what config file to open,
rather than using the re-written domain name provided by the
UseCanonicalName setting, or even by doing a lookup of the
configured ServerName for the VirtualHost section.
The workaround you (mimo) suggest isn't very easy to work
with, as this is for a shared web server which can host hundreds
of domains, and there are some scripts which I have created to
manipulate the config file settings to enable/disable certain
settings. To now have to make it manipulate at least 2 more
(one for www.domain.com, another for the dedicated IP) config
files at the same time to ensure settings are identical would just
be silly. There *has* to be a better way, and I truly believe that
a change in mod_frontpage.c holds the answer to that.
Logged In: YES
user_id=104595
No, it is already assigned to the virtual host before this
module acts.
The fix should be obvious -- have the module check the
environment variable SERVER_NAME to get the canonical server
name (ie defined in the virtualhost block and used by
frontpage) before looking for the configuration file.