Hi,
I have an apache server running on a machine with settings in
httpd.conf:
Listen 1.2.3.4:80
Now I want to assign a domain name 'www.xyz.com' to it.So I put the
servername as 'www.xyz.com' in the httpd.conf file.Now when I access
'www.xyz.com' from browser, it works fine. But the problem is that it
is showing http://1.2.3.4/ instead of my domain name in the addressbar.
The domain name by itself replaced by the IP address of the machine.
Any idea what is happening here.
With regards.

PS: I am posting this again in a different subject(suitable for search)
to help someone facing the same prob.

just.starting@gmail.com wrote:

I believe you've set this option to "on":
http://httpd.apache.org/docs/1.3/mod...ecanonicalname

--
Kim André Akerø
- kimandre@NOSPAMbetadome.com
(remove NOSPAM to contact me directly)

yes. the usecanonicalname option is on in the httpd.conf file, still
the browser is showing the ipaddress instead of domain name.

just.starting@gmail.com wrote:

What happens if you set this option to "no"?

(Remember to restart Apache each time you make changes to httpd.conf to
be able to see the result of those changes.)

--
Kim André Akerø
- kimandre@NOSPAMbetadome.com
(remove NOSPAM to contact me directly)

And lo, Kim André Akerø didst speak in alt.www.webmaster:

Not "no". It should be "Off". I had a similar row with the people who
host my employer's website; It took three months of pleading before they
decided to "risk" changing it from "On" to "Off". It actually sounded
like no one there knew what the command even did before I told them.

Grey

--
The technical axiom that nothing is impossible sinisterly implies the
pitfall corollary that nothing is ridiculous.
- http://www.greywyvern.com/orca#sear - Orca Search: Full-featured spider
and site-search engine

GreyWyvern wrote:

Of course, I did mean "Off"... I can blame that on being slightly
unfocused.

Good thing I don't make that kind of mistakes when configuring a server
myself.

Doesn't sound too good. Most installations of Apache comes with a
well-commented httpd.conf file, with rough explanations for the
majority of the configuration directives.

Also, I find it hard to believe that it takes them three months just to
make them look up the configuration option in the manual. It would've
taken me about 10 minutes of research (from the minute I plug in my
laptop to an Internet connection).

--
Kim André Akerø
- kimandre@NOSPAMbetadome.com
(remove NOSPAM to contact me directly)

And lo, Kim André Akerø didst speak in alt.www.webmaster:

It wasn't that they didn't look up what it did after I told them I would
need it... It's that they were very timid about making conf changes to a
live server. They told me this and I asked them if they didn't have any
test servers set up; to which they replied that they did, but it would
take too long to set it up to match the existing configuration of our
server, just to test one new config line.

In the end, stopping my whining seemed to be what made the change worth it
to them

Grey

--
The technical axiom that nothing is impossible sinisterly implies the
pitfall corollary that nothing is ridiculous.
- http://www.greywyvern.com/orca#sear - Orca Search: Full-featured spider
and site-search engine