× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Oops, sorry, I hit enter before I answered your second question.

In the second case, you just have to remember that whatever is in the <link href="x"> is relative to your DocumentRoot.  So if you have:

DocumentRoot /www/abc/htdocs

And you also have

<link rel="icon" type="image/icon" href="/abc/images/favicon.ico" />

Then your icon should be located here in the IFS:

/www/abc/htdocs/abc/images/favicon.ico

All URLs are relative to the DocumentRoot, unless an Alias/ScriptAlias is used.

-SK

On 9/23/19 11:56 PM, Scott Klement wrote:
That would be the directory pointed to by the DocumentRoot directive. For example:

DocumentRoot /www/abc/htdocs

So you would make your image be /www/abc/htdocs/favicon.ico

It's whatever directory your DocumentRoot points to.

-SK

On 9/23/19 11:36 PM, Jim Franz wrote:
I want to add a favicon.ico to a cgi website.
Everything google says to put it in the "root" directory.
What is the root directory of a server instance?
If my instance is abc and Apache set up as /www/abc
and added  /www/abc/favicon.ico
getting log errors  ZSRV_MSG0016:

read that i can put header directive to my images directory
<link rel="shortcut icon" type="image/x-icon"
href="/abc/images/favicon.ico" />
still getting error
ZSRV_MSG0016: URI in request GET /abc/images/favicon.ico HTTP/1.1 is not
valid
Where can i put this file to work but not open up that directory to the web?

Jim


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.