Relying on DOCUMENT_ROOT environment variable
Tintin
spec?
--
PLEASE NOTE: comp.infosystems.www.authoring.cgi is a
SELF-MODERATED newsgroup. aa.net and boutell.com are
NOT the originators of the articles and are NOT responsible
for their content. You can SELF-APPROVE your first posting
by writing the word 'passme' on a line by itself.
Alan J. Flavell
: Can I rely on the DOCUMENT_ROOT environment variable? Is it part of the CGI
: spec?
Why are you asking us? Don't you know where to find the spec, nor how
to consult the relevant FAQ resources? Seems to me you've been around
here for long enough that you ought to know better by now than to ask
FAQs.
http://www.smithrenaud.com/public/CGI_MetaFAQ.html#cgi_spec
brian, have you considered adding the draft RFC spec to this?
Nick, how about you?
The URL http://www.golux.com/coar/cgi/ seems pretty stable to me,
though I guess Ken might appreciate a note from you if you are
intending to cite it.
On your specific point, http://www.apache.org/docs/mod/mod_cgi.html
shows that Apache will establish that environment variable, in
addition to those that are "described in the CGI specification". But
you can see for yourself (and should have done so before asking!) that
it's not listed in the CGI spec.
cheers
Tintin
"Alan J. Flavell" <fla...@mail.cern.ch> wrote in message
news:Pine.GHP.4.21.00050...@hpplus01.cern.ch...
: On 5 May 2000, Tintin wrote:
:
: : Can I rely on the DOCUMENT_ROOT environment variable? Is it part of the
CGI
: : spec?
:
: Why are you asking us? Don't you know where to find the spec, nor how
: to consult the relevant FAQ resources? Seems to me you've been around
: here for long enough that you ought to know better by now than to ask
: FAQs.
:
: http://www.smithrenaud.com/public/CGI_MetaFAQ.html#cgi_spec
:
: brian, have you considered adding the draft RFC spec to this?
: Nick, how about you?
:
: The URL http://www.golux.com/coar/cgi/ seems pretty stable to me,
: though I guess Ken might appreciate a note from you if you are
: intending to cite it.
:
: On your specific point, http://www.apache.org/docs/mod/mod_cgi.html
: shows that Apache will establish that environment variable, in
: addition to those that are "described in the CGI specification". But
: you can see for yourself (and should have done so before asking!) that
: it's not listed in the CGI spec.
Thanks Alan.
You are quite right about me looking it up in the FAQ's. I don't know what
came over me.
brian d foy
:http://www.smithrenaud.com/public/CGI_MetaFAQ.html#cgi_spec
:brian, have you considered adding the draft RFC spec to this?
the problem is that it's a draft. if it were *the* specification,
then that would be the one i'd reference. however, i don't intend
to take aim on a moving target ;)
feel free to educate me though. :)
--
brian d foy
Perl Mongers <URI:http://www.perl.org>
CGI MetaFAQ
<URI:http://www.smithrenaud.com/public/CGI_MetaFAQ.html>
Alan J. Flavell
: :http://www.smithrenaud.com/public/CGI_MetaFAQ.html#cgi_spec
:
: :brian, have you considered adding the draft RFC spec to this?
:
: the problem is that it's a draft.
I can't argue with that.
: feel free to educate me though. :)
Well, myself I feel that the NCSA reference is now a bit of an
antique; although I don't see anything in there that's actively
_wrong_, there seem to me to be a lot of gaps in what is actually
covered, and also a number of implicit unix-specific assumptions which
the draft RFC is trying to distance itself from; I would rather like
readers' attention to be drawn to the fact that there _is_ work in
progress, even though it's still not finalised.
However, it's your FAQ, and obviously I can do no more than try gentle
persuasion as to what goes in it. I can quite understand your
reservations on citing something that is still a draft /
work-in-progress.
cheers
brian d foy
:On 6 May 2000, brian d foy wrote:
:
:: :http://www.smithrenaud.com/public/CGI_MetaFAQ.html#cgi_spec
::
:: :brian, have you considered adding the draft RFC spec to this?
::
:: the problem is that it's a draft.
:
:I can't argue with that.
:
:: feel free to educate me though. :)
:However, it's your FAQ, and obviously I can do no more than try gentle
:persuasion as to what goes in it. I can quite understand your
:reservations on citing something that is still a draft /
:work-in-progress.
i'll put in both. :) what's the canonical address for it?
--
brian d foy
Perl Mongers <URI:http://www.perl.org>
CGI MetaFAQ
<URI:http://www.smithrenaud.com/public/CGI_MetaFAQ.html>
--
Alan J. Flavell
: i'll put in both. :) what's the canonical address for it?
Good call. It answers to www.golux.com, but now that I look more
closely (aside from the relative URLs, from which one can deduce
nothing), the one explicit reference by the author to his own site
calls it web.golux.com. Apologies, I hadn't noticed that before.
So I guess it's http://web.golux.com/coar/cgi/ , although it also
answers to the other name.
As I said before, I feel sure he'd appreciate a brief note if you
intending to cite it. That could help clarify the preferred URL name
too, but the other links to the site on the WWW seem to use the
web.golux.com name.
Jerome O'Neil
br...@smithrenaud.com (brian d foy) writes:
: In article <Pine.GHP.4.21.00050...@hpplus01.cern.ch>, "Alan J. Flavell" <fla...@mail.cern.ch> wrote:
:
::http://www.smithrenaud.com/public/CGI_MetaFAQ.html#cgi_spec
:
::brian, have you considered adding the draft RFC spec to this?
:
: then that would be the one i'd reference. however, i don't intend
: to take aim on a moving target ;)
I don't think draft status should prevent you from using it as a guide,
so long as it's on standards track.
If you're taking votes, I vote put it up!
brian d foy
: In article <brian-06050...@202.portland-05rs.me.dial-access.att.net>,
: br...@smithrenaud.com (brian d foy) writes:
: : In article <Pine.GHP.4.21.00050...@hpplus01.cern.ch>, "Alan J. Flavell" <fla...@mail.cern.ch> wrote:
: :
: ::http://www.smithrenaud.com/public/CGI_MetaFAQ.html#cgi_spec
: :
: ::brian, have you considered adding the draft RFC spec to this?
: :
: : the problem is that it's a draft.
: I don't think draft status should prevent you from using it as a guide,
: so long as it's on standards track.
: If you're taking votes, I vote put it up!
i'll update it next week. while i'm at it, anything else that is
missing? :)
--
brian d foy
CGI Meta FAQ <URL:http://www.smithrenaud.com/public/CGI_MetaFAQ.html>
Perl Mongers <URL:http://www.perl.org/>
Alan J. Flavell
[email and post]
On 8 May 2000, brian d foy wrote:
: i'll update it next week. while i'm at it, anything else that is
: missing? :)
Well, seeing as you asked (you do appreciate this is meant to be
constructive, yes?):
* under the HTTP heading, HTTP/1.1 is now defined by RFC2616, as you
obviously already know
Xenu link check reports the following errors:
http://www.smithrenaud.com/public/CGI_MetaFAQ.html
http://www.fastcgi.com/words/FAQ.htm
\_____ error code: 404 (not found)
* The fastcgi home page makes no mention of an FAQ. Maybe you want to
just cite the home page.
http://www.illuminatus.com/cookie.fcgi
\_____ error code: 503 (temporarily overloaded)
* The reference to "503 temporarily overloaded" seems to be a spoof,
maybe xenu is confused by our proxy cache. In reality the proxy
reports "connection refused". The problem might be temporary, though.
I drew a blank with search for alternative location.
http://www3.pair.com/webthing/cgiplusplus/
\_____ error code: 404 (not found)
* cgiplusplus can be found at http://www.webthing.com/cgiplusplus/
unless Nick chips in with a new URL,
http://www.cs.hmc.edu/~sbooth/cgicc/
\_____ error code: 404 (not found)
* cgicc (now "GNU Cgicc") seems to be at
http://www.lanminds.com/~sbooth/cgicc/
http://www1.dpe.net/C++/
\_____ error code: 400 (no object data)
* Martin's CGI.h was spotted at http://www.marketrends.net/C++/
http://www-itg.lbl.gov/~clarsen/projects/htcl/http-proc-args.html
\_____ error code: 404 (not found)
* "Processing of CGI GET script arguments under TCL"
http://www.math.utah.edu/~beebe/support/htcl-0.1/htcl/http-proc-args.html
http://tcltk.anu.edu.au/tclweb/cgi.html
\_____ error code: 504 (timed out waiting for gateway)
* CGI programming using TCL: I drew a blank on that one, sorry.
Now the redirections:
http://hoohoo.ncsa.uiuc.edu/cgi-1.1
redirected to: http://hoohoo.ncsa.uiuc.edu/cgi-1.1/
(missed a trailing '/')
http://help.netscape.com/kb/server/960513-111.html
redirected to: http://help.netscape.com/kb/corporate/960513-111.html
seems to have moved
http://www-genome.wi.mit.edu/ftp/pub/software/WWW/cgi_docs.htm
redirected to: http://stein.cshl.org/WWW/software/CGI/cgi_docs.htm
this too
http://www-genome.wi.mit.edu/WWW/faqs/www-security-faq.html
redirected to: http://www.w3.org/Security/Faq/www-security-faq.html
and this
http://www.perl.com/
redirected to: http://www.perl.com/pub
that might be a deliberate technical redirection(?)
http://language.perl.com/CPAN/doc/FAQs/cgi/perl-cgi-faq.html
redirected to: http://www.perl.com/CPAN/doc/FAQs/cgi/perl-cgi-faq.html
another site move, isn't it?
http://help.netscape.com/kb/client/970226-2.html
redirected to: http://help.netscape.com/kb/consumer/970226-2.html
another netscape move similar to the above
http://language.perl.com/CPAN/doc/FAQs/cgi/idiots-guide.html
redirected to: http://www.perl.com/CPAN/doc/FAQs/cgi/idiots-guide.html
and again.
Hope those were useful, don't take it the wrong way, I've only
posted this in public as those affected (Nick for example) might
have better answers to the points raised.
Jerome O'Neil
:: I don't think draft status should prevent you from using it as a guide,
:: so long as it's on standards track.
:
:: If you're taking votes, I vote put it up!
:
: i'll update it next week. while i'm at it, anything else that is
: missing? :)
My beer-batter corndog recipie, but thats a state secret...
brian d foy
:[email and post]
:
:On 8 May 2000, brian d foy wrote:
:
:: i'll update it next week. while i'm at it, anything else that is
:: missing? :)
:
:Well, seeing as you asked (you do appreciate this is meant to be
:constructive, yes?):
[snip]
that's what i get for neglecting that document for so long ;)
anyway, all of the references have been fixed, and the draft CGI RFC
reference has been added.
--
brian d foy
Perl Mongers <URI:http://www.perl.org>
CGI MetaFAQ
<URI:http://www.smithrenaud.com/public/CGI_MetaFAQ.html>
--
Nick Kew
"Alan J. Flavell" <fla...@mail.cern.ch> writes:
: Nick, how about you?
Eeek - I was sure I'd put that in to the latest version, and that it had
propagated to all the canonical sites. Hasn't it reached you?
--
Nick Kew
We're so advanced here ... our nearest main road is A 386
Alan J. Flavell
[posted and emailed]
On 10 May 2000, Nick Kew wrote:
: In article <Pine.GHP.4.21.00050...@hpplus01.cern.ch>,
: "Alan J. Flavell" <fla...@mail.cern.ch> writes:
:
: : Nick, how about you?
:
: Eeek - I was sure I'd put that in to the latest version,
Nick, please accept my apology, it seems I hadn't done my homework
properly.
all the best