➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author majid
Recipients christian.heimes, gregory.p.smith, jafo, loewis, majid, terry.reedy
Date 2010-08-05.19:56:39
SpamBayes Score 4.972867e-05
Marked as misclassified No
Message-id <1281038203.78.0.682551230461.issue1684@psf.upfronthosting.co.za>
In-reply-to
Content 
Well, CGI/1.1 was formally documented by RFC 3875 in October 2004 (a full 11 years after CGI was introduced...).
http://www.rfc-editor.org/rfc/rfc3875.txt

The RFC is classified as "informative", but it's as close to a definitive spec for CGI as we will ever get. Section 7 described the system-specific implementation notes, and 7.2 specifies UNIX in particular:

The current working directory
      The current working directory for the script SHOULD be set to the
      directory containing the script.

This is also the specified behavior for AmugaDOS and EBCDIC POSIX systems. Oddly enough, the RFC editor did not find it worthwhile to specify the behavior on Windows...
History
Date User Action Args
2010-08-05 19:56:44majidsetrecipients: + majid, loewis, terry.reedy, gregory.p.smith, jafo, christian.heimes
2010-08-05 19:56:43majidsetmessageid: <1281038203.78.0.682551230461.issue1684@psf.upfronthosting.co.za>
2010-08-05 19:56:40majidlinkissue1684 messages
2010-08-05 19:56:39majidcreate