You said:
My fear is that the the phrase "$ENV{SCRIPT_NAME}" is stored as part of the \$hnbinURL variable
then \$hnbinURL is EVALed at various times throughout the program, coming up with different,
faulty values everywhere.
The hnrc file is loaded first thing in every HyperNews script,
and that causes the evaluation of "$ENV{'SCRIPT_NAME'}" at that
time only. So it might be different for each access if somehow
the scripts are called differently each time. The problem is
not so much that difference per se, but the fact that the
path that is returned is absolute to the file system, rather than
relative to the server root.
You could replace that whole block of assignments to $hnbinURL
with one explicit line:
$hnbinURL = "http://www.frontier-news.com/HyperNews/
Alternatively, you might try leaving $hnbinURL empty,
and give an explicit, full URL for the $hniconsURL. The only
use of $hnbinURL is to prepend it to various things that really
should not have that dependency in the first place. In all
cases that I am aware of, this prefix is deleted anyway. It is
historical, and I've been meaning to root it out, so to speak.
|
No end of problems, from my perspective anyway 
HyperNews' setup-form wants to tack on a unix path to a URL.
(Steven Peterson)
Oops - my mistake
by liberte@hypernews.org, 1996, Feb 01
