SSH

[John Abreau]

This is actually the standard, documented behavior for NCSA httpd and
Apache. If the ServerName directive is defined, then the url is rewritten
as http://${ServerName}:${Port}/rest/of/url/ if it's a directory and
doesn't include the trailing slash. If ServerName is defined, then it
*must* be a valid FQDN for itself.

On Thu, 18 Mar 1999, Rich Braun wrote:

> Jabr wrote:
> > If you try to access http://209.6.162.179/download (no slash at the end),
> > the server does a redirect to www.ici.net. If you instead try
> > http://209.6.162.179/download/ (a slash at the end), then it works.
> 
> Hmm, puzzling.  Attached is my httpd.conf file (just upgraded
> everything on my Linux box, including Apache, because of security
> paranoia now that I'm on a high-visibility cable network); I'll look
> at it after I get back from a trip unless I get a chance the next
> couple of days.  If any of you have suggestions on this config, I'd
> be happy to incorporate them.
> :
> :
> ServerName www.ci.net

--
John Abreau / Executive Director, Boston Linux & Unix 
Email: jabr at blu.org / URL: http://www.blu.org
ICQ#28611923
-----------------------------------------------------------------------
    Your mouse has moved. Windows NT must be restarted for the change
    to take effect. Reboot now?  [ OK ]
-----------------------------------------------------------------------




-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).