This is my first CGI script

Error

name:\", form[\"name\"].value)\n" "print(\"

addr:\", form[\"addr\"].value)\n" "...further form processing here..." msgstr "" #: library/cgi.rst:136 msgid "" "Here the fields, accessed through ``form[key]``, are themselves instances " "of :class:`FieldStorage` (or :class:`MiniFieldStorage`, depending on the " "form encoding). The :attr:`~FieldStorage.value` attribute of the instance " "yields the string value of the field. The :meth:`~FieldStorage.getvalue` " "method returns this string value directly; it also accepts an optional " "second argument as a default to return if the requested key is not present." msgstr "" #: library/cgi.rst:143 msgid "" "If the submitted form data contains more than one field with the same name, " "the object retrieved by ``form[key]`` is not a :class:`FieldStorage` or :" "class:`MiniFieldStorage` instance but a list of such instances. Similarly, " "in this situation, ``form.getvalue(key)`` would return a list of strings. If " "you expect this possibility (when your HTML form contains multiple fields " "with the same name), use the :meth:`~FieldStorage.getlist` method, which " "always returns a list of values (so that you do not need to special-case the " "single item case). For example, this code concatenates any number of " "username fields, separated by commas::" msgstr "" #: library/cgi.rst:153 msgid "" "value = form.getlist(\"username\")\n" "usernames = \",\".join(value)" msgstr "" #: library/cgi.rst:156 msgid "" "If a field represents an uploaded file, accessing the value via the :attr:" "`~FieldStorage.value` attribute or the :meth:`~FieldStorage.getvalue` method " "reads the entire file in memory as bytes. This may not be what you want. " "You can test for an uploaded file by testing either the :attr:`~FieldStorage." "filename` attribute or the :attr:`~FieldStorage.file` attribute. You can " "then read the data from the :attr:`!file` attribute before it is " "automatically closed as part of the garbage collection of the :class:" "`FieldStorage` instance (the :func:`~io.RawIOBase.read` and :func:`~io." "IOBase.readline` methods will return bytes)::" msgstr "" #: library/cgi.rst:167 msgid "" "fileitem = form[\"userfile\"]\n" "if fileitem.file:\n" " # It's an uploaded file; count lines\n" " linecount = 0\n" " while True:\n" " line = fileitem.file.readline()\n" " if not line: break\n" " linecount = linecount + 1" msgstr "" #: library/cgi.rst:176 msgid "" ":class:`FieldStorage` objects also support being used in a :keyword:`with` " "statement, which will automatically close them when done." msgstr "" #: library/cgi.rst:179 msgid "" "If an error is encountered when obtaining the contents of an uploaded file " "(for example, when the user interrupts the form submission by clicking on a " "Back or Cancel button) the :attr:`~FieldStorage.done` attribute of the " "object for the field will be set to the value -1." msgstr "" #: library/cgi.rst:184 msgid "" "The file upload draft standard entertains the possibility of uploading " "multiple files from one field (using a recursive :mimetype:`multipart/\\*` " "encoding). When this occurs, the item will be a dictionary-like :class:" "`FieldStorage` item. This can be determined by testing its :attr:`!type` " "attribute, which should be :mimetype:`multipart/form-data` (or perhaps " "another MIME type matching :mimetype:`multipart/\\*`). In this case, it can " "be iterated over recursively just like the top-level form object." msgstr "" #: library/cgi.rst:192 msgid "" "When a form is submitted in the \"old\" format (as the query string or as a " "single data part of type :mimetype:`application/x-www-form-urlencoded`), the " "items will actually be instances of the class :class:`MiniFieldStorage`. In " "this case, the :attr:`!list`, :attr:`!file`, and :attr:`filename` attributes " "are always ``None``." msgstr "" #: library/cgi.rst:197 msgid "" "A form submitted via POST that also has a query string will contain both :" "class:`FieldStorage` and :class:`MiniFieldStorage` items." msgstr "" #: library/cgi.rst:200 msgid "" "The :attr:`~FieldStorage.file` attribute is automatically closed upon the " "garbage collection of the creating :class:`FieldStorage` instance." msgstr "" #: library/cgi.rst:204 msgid "" "Added support for the context management protocol to the :class:" "`FieldStorage` class." msgstr "" #: library/cgi.rst:210 msgid "Higher Level Interface" msgstr "" #: library/cgi.rst:212 msgid "" "The previous section explains how to read CGI form data using the :class:" "`FieldStorage` class. This section describes a higher level interface which " "was added to this class to allow one to do it in a more readable and " "intuitive way. The interface doesn't make the techniques described in " "previous sections obsolete --- they are still useful to process file uploads " "efficiently, for example." msgstr "" #: library/cgi.rst:221 msgid "" "The interface consists of two simple methods. Using the methods you can " "process form data in a generic way, without the need to worry whether only " "one or more values were posted under one name." msgstr "" #: library/cgi.rst:225 msgid "" "In the previous section, you learned to write following code anytime you " "expected a user to post more than one value under one name::" msgstr "" #: library/cgi.rst:228 msgid "" "item = form.getvalue(\"item\")\n" "if isinstance(item, list):\n" " # The user is requesting more than one item.\n" "else:\n" " # The user is requesting only one item." msgstr "" #: library/cgi.rst:234 msgid "" "This situation is common for example when a form contains a group of " "multiple checkboxes with the same name::" msgstr "" #: library/cgi.rst:237 msgid "" "\n" "" msgstr "" #: library/cgi.rst:240 msgid "" "In most situations, however, there's only one form control with a particular " "name in a form and then you expect and need only one value associated with " "this name. So you write a script containing for example this code::" msgstr "" #: library/cgi.rst:244 msgid "user = form.getvalue(\"user\").upper()" msgstr "" #: library/cgi.rst:246 msgid "" "The problem with the code is that you should never expect that a client will " "provide valid input to your scripts. For example, if a curious user appends " "another ``user=foo`` pair to the query string, then the script would crash, " "because in this situation the ``getvalue(\"user\")`` method call returns a " "list instead of a string. Calling the :meth:`~str.upper` method on a list " "is not valid (since lists do not have a method of this name) and results in " "an :exc:`AttributeError` exception." msgstr "" #: library/cgi.rst:254 msgid "" "Therefore, the appropriate way to read form data values was to always use " "the code which checks whether the obtained value is a single value or a list " "of values. That's annoying and leads to less readable scripts." msgstr "" #: library/cgi.rst:258 msgid "" "A more convenient approach is to use the methods :meth:`~FieldStorage." "getfirst` and :meth:`~FieldStorage.getlist` provided by this higher level " "interface." msgstr "" #: library/cgi.rst:264 msgid "" "This method always returns only one value associated with form field *name*. " "The method returns only the first value in case that more values were posted " "under such name. Please note that the order in which the values are " "received may vary from browser to browser and should not be counted on. " "[#]_ If no such form field or value exists then the method returns the " "value specified by the optional parameter *default*. This parameter " "defaults to ``None`` if not specified." msgstr "" #: library/cgi.rst:275 msgid "" "This method always returns a list of values associated with form field " "*name*. The method returns an empty list if no such form field or value " "exists for *name*. It returns a list consisting of one item if only one " "such value exists." msgstr "" #: library/cgi.rst:279 msgid "Using these methods you can write nice compact code::" msgstr "" #: library/cgi.rst:281 msgid "" "import cgi\n" "form = cgi.FieldStorage()\n" "user = form.getfirst(\"user\", \"\").upper() # This way it's safe.\n" "for item in form.getlist(\"item\"):\n" " do_something(item)" msgstr "" #: library/cgi.rst:291 msgid "Functions" msgstr "" #: library/cgi.rst:293 msgid "" "These are useful if you want more control, or if you want to employ some of " "the algorithms implemented in this module in other circumstances." msgstr "" #: library/cgi.rst:299 msgid "" "Parse a query in the environment or from a file (the file defaults to ``sys." "stdin``). The *keep_blank_values*, *strict_parsing* and *separator* " "parameters are passed to :func:`urllib.parse.parse_qs` unchanged." msgstr "" #: library/cgi.rst:303 msgid "" "This function, like the rest of the :mod:`cgi` module, is deprecated. It can " "be replaced by calling :func:`urllib.parse.parse_qs` directly on the desired " "query string (except for ``multipart/form-data`` input, which can be handled " "as described for :func:`parse_multipart`)." msgstr "" #: library/cgi.rst:312 msgid "" "Parse input of type :mimetype:`multipart/form-data` (for file uploads). " "Arguments are *fp* for the input file, *pdict* for a dictionary containing " "other parameters in the :mailheader:`Content-Type` header, and *encoding*, " "the request encoding." msgstr "" #: library/cgi.rst:317 msgid "" "Returns a dictionary just like :func:`urllib.parse.parse_qs`: keys are the " "field names, each value is a list of values for that field. For non-file " "fields, the value is a list of strings." msgstr "" #: library/cgi.rst:321 msgid "" "This is easy to use but not much good if you are expecting megabytes to be " "uploaded --- in that case, use the :class:`FieldStorage` class instead which " "is much more flexible." msgstr "" #: library/cgi.rst:325 msgid "" "Added the *encoding* and *errors* parameters. For non-file fields, the " "value is now a list of strings, not bytes." msgstr "" #: library/cgi.rst:329 msgid "Added the *separator* parameter." msgstr "" #: library/cgi.rst:332 msgid "" "This function, like the rest of the :mod:`cgi` module, is deprecated. It can " "be replaced with the functionality in the :mod:`email` package (e.g. :class:" "`email.message.EmailMessage`/:class:`email.message.Message`) which " "implements the same MIME RFCs, or with the :pypi:`multipart` PyPI project." msgstr "" #: library/cgi.rst:342 msgid "" "Parse a MIME header (such as :mailheader:`Content-Type`) into a main value " "and a dictionary of parameters." msgstr "" #: library/cgi.rst:345 msgid "" "This function, like the rest of the :mod:`cgi` module, is deprecated. It can " "be replaced with the functionality in the :mod:`email` package, which " "implements the same MIME RFCs." msgstr "" #: library/cgi.rst:350 msgid "For example, with :class:`email.message.EmailMessage`::" msgstr "" #: library/cgi.rst:352 msgid "" "from email.message import EmailMessage\n" "msg = EmailMessage()\n" "msg['content-type'] = 'application/json; charset=\"utf8\"'\n" "main, params = msg.get_content_type(), msg['content-type'].params" msgstr "" #: library/cgi.rst:360 msgid "" "Robust test CGI script, usable as main program. Writes minimal HTTP headers " "and formats all information provided to the script in HTML format." msgstr "" #: library/cgi.rst:366 msgid "Format the shell environment in HTML." msgstr "" #: library/cgi.rst:371 msgid "Format a form in HTML." msgstr "" #: library/cgi.rst:376 msgid "Format the current directory in HTML." msgstr "" #: library/cgi.rst:381 msgid "Print a list of useful (used by CGI) environment variables in HTML." msgstr "" #: library/cgi.rst:387 msgid "Caring about security" msgstr "" #: library/cgi.rst:391 msgid "" "There's one important rule: if you invoke an external program (via :func:`os." "system`, :func:`os.popen` or other functions with similar functionality), " "make very sure you don't pass arbitrary strings received from the client to " "the shell. This is a well-known security hole whereby clever hackers " "anywhere on the web can exploit a gullible CGI script to invoke arbitrary " "shell commands. Even parts of the URL or field names cannot be trusted, " "since the request doesn't have to come from your form!" msgstr "" #: library/cgi.rst:399 msgid "" "To be on the safe side, if you must pass a string gotten from a form to a " "shell command, you should make sure the string contains only alphanumeric " "characters, dashes, underscores, and periods." msgstr "" #: library/cgi.rst:405 msgid "Installing your CGI script on a Unix system" msgstr "" #: library/cgi.rst:407 msgid "" "Read the documentation for your HTTP server and check with your local system " "administrator to find the directory where CGI scripts should be installed; " "usually this is in a directory :file:`cgi-bin` in the server tree." msgstr "" #: library/cgi.rst:411 msgid "" "Make sure that your script is readable and executable by \"others\"; the " "Unix file mode should be ``0o755`` octal (use ``chmod 0755 filename``). " "Make sure that the first line of the script contains ``#!`` starting in " "column 1 followed by the pathname of the Python interpreter, for instance::" msgstr "" #: library/cgi.rst:416 msgid "#!/usr/local/bin/python" msgstr "" #: library/cgi.rst:418 msgid "" "Make sure the Python interpreter exists and is executable by \"others\"." msgstr "" #: library/cgi.rst:420 msgid "" "Make sure that any files your script needs to read or write are readable or " "writable, respectively, by \"others\" --- their mode should be ``0o644`` for " "readable and ``0o666`` for writable. This is because, for security reasons, " "the HTTP server executes your script as user \"nobody\", without any special " "privileges. It can only read (write, execute) files that everybody can read " "(write, execute). The current directory at execution time is also different " "(it is usually the server's cgi-bin directory) and the set of environment " "variables is also different from what you get when you log in. In " "particular, don't count on the shell's search path for executables (:envvar:" "`PATH`) or the Python module search path (:envvar:`PYTHONPATH`) to be set to " "anything interesting." msgstr "" #: library/cgi.rst:431 msgid "" "If you need to load modules from a directory which is not on Python's " "default module search path, you can change the path in your script, before " "importing other modules. For example::" msgstr "" #: library/cgi.rst:435 msgid "" "import sys\n" "sys.path.insert(0, \"/usr/home/joe/lib/python\")\n" "sys.path.insert(0, \"/usr/local/lib/python\")" msgstr "" #: library/cgi.rst:439 msgid "(This way, the directory inserted last will be searched first!)" msgstr "" #: library/cgi.rst:441 msgid "" "Instructions for non-Unix systems will vary; check your HTTP server's " "documentation (it will usually have a section on CGI scripts)." msgstr "" #: library/cgi.rst:446 msgid "Testing your CGI script" msgstr "" #: library/cgi.rst:448 msgid "" "Unfortunately, a CGI script will generally not run when you try it from the " "command line, and a script that works perfectly from the command line may " "fail mysteriously when run from the server. There's one reason why you " "should still test your script from the command line: if it contains a syntax " "error, the Python interpreter won't execute it at all, and the HTTP server " "will most likely send a cryptic error to the client." msgstr "" #: library/cgi.rst:455 msgid "" "Assuming your script has no syntax errors, yet it does not work, you have no " "choice but to read the next section." msgstr "" #: library/cgi.rst:460 msgid "Debugging CGI scripts" msgstr "" #: library/cgi.rst:464 msgid "" "First of all, check for trivial installation errors --- reading the section " "above on installing your CGI script carefully can save you a lot of time. " "If you wonder whether you have understood the installation procedure " "correctly, try installing a copy of this module file (:file:`cgi.py`) as a " "CGI script. When invoked as a script, the file will dump its environment " "and the contents of the form in HTML format. Give it the right mode etc., " "and send it a request. If it's installed in the standard :file:`cgi-bin` " "directory, it should be possible to send it a request by entering a URL into " "your browser of the form:" msgstr "" #: library/cgi.rst:473 msgid "http://yourhostname/cgi-bin/cgi.py?name=Joe+Blow&addr=At+Home" msgstr "" #: library/cgi.rst:477 msgid "" "If this gives an error of type 404, the server cannot find the script -- " "perhaps you need to install it in a different directory. If it gives " "another error, there's an installation problem that you should fix before " "trying to go any further. If you get a nicely formatted listing of the " "environment and form content (in this example, the fields should be listed " "as \"addr\" with value \"At Home\" and \"name\" with value \"Joe Blow\"), " "the :file:`cgi.py` script has been installed correctly. If you follow the " "same procedure for your own script, you should now be able to debug it." msgstr "" #: library/cgi.rst:486 msgid "" "The next step could be to call the :mod:`cgi` module's :func:`test` function " "from your script: replace its main code with the single statement ::" msgstr "" #: library/cgi.rst:489 msgid "cgi.test()" msgstr "" #: library/cgi.rst:491 msgid "" "This should produce the same results as those gotten from installing the :" "file:`cgi.py` file itself." msgstr "" #: library/cgi.rst:494 msgid "" "When an ordinary Python script raises an unhandled exception (for whatever " "reason: of a typo in a module name, a file that can't be opened, etc.), the " "Python interpreter prints a nice traceback and exits. While the Python " "interpreter will still do this when your CGI script raises an exception, " "most likely the traceback will end up in one of the HTTP server's log files, " "or be discarded altogether." msgstr "" #: library/cgi.rst:501 msgid "" "Fortunately, once you have managed to get your script to execute *some* " "code, you can easily send tracebacks to the web browser using the :mod:" "`cgitb` module. If you haven't done so already, just add the lines::" msgstr "" #: library/cgi.rst:508 msgid "" "to the top of your script. Then try running it again; when a problem " "occurs, you should see a detailed report that will likely make apparent the " "cause of the crash." msgstr "" #: library/cgi.rst:512 msgid "" "If you suspect that there may be a problem in importing the :mod:`cgitb` " "module, you can use an even more robust approach (which only uses built-in " "modules)::" msgstr "" #: library/cgi.rst:515 msgid "" "import sys\n" "sys.stderr = sys.stdout\n" "print(\"Content-Type: text/plain\")\n" "print()\n" "...your code here..." msgstr "" #: library/cgi.rst:521 msgid "" "This relies on the Python interpreter to print the traceback. The content " "type of the output is set to plain text, which disables all HTML " "processing. If your script works, the raw HTML will be displayed by your " "client. If it raises an exception, most likely after the first two lines " "have been printed, a traceback will be displayed. Because no HTML " "interpretation is going on, the traceback will be readable." msgstr "" #: library/cgi.rst:530 msgid "Common problems and solutions" msgstr "" #: library/cgi.rst:532 msgid "" "Most HTTP servers buffer the output from CGI scripts until the script is " "completed. This means that it is not possible to display a progress report " "on the client's display while the script is running." msgstr "" #: library/cgi.rst:536 msgid "Check the installation instructions above." msgstr "" #: library/cgi.rst:538 msgid "" "Check the HTTP server's log files. (``tail -f logfile`` in a separate " "window may be useful!)" msgstr "" #: library/cgi.rst:541 msgid "" "Always check a script for syntax errors first, by doing something like " "``python script.py``." msgstr "" #: library/cgi.rst:544 msgid "" "If your script does not have any syntax errors, try adding ``import cgitb; " "cgitb.enable()`` to the top of the script." msgstr "" #: library/cgi.rst:547 msgid "" "When invoking external programs, make sure they can be found. Usually, this " "means using absolute path names --- :envvar:`PATH` is usually not set to a " "very useful value in a CGI script." msgstr "" #: library/cgi.rst:551 msgid "" "When reading or writing external files, make sure they can be read or " "written by the userid under which your CGI script will be running: this is " "typically the userid under which the web server is running, or some " "explicitly specified userid for a web server's ``suexec`` feature." msgstr "" #: library/cgi.rst:556 msgid "" "Don't try to give a CGI script a set-uid mode. This doesn't work on most " "systems, and is a security liability as well." msgstr "" #: library/cgi.rst:560 msgid "Footnotes" msgstr "" #: library/cgi.rst:561 msgid "" "Note that some recent versions of the HTML specification do state what order " "the field values should be supplied in, but knowing whether a request was " "received from a conforming browser, or even from a browser at all, is " "tedious and error-prone." msgstr "" #: library/cgi.rst:10 msgid "WWW" msgstr "" #: library/cgi.rst:10 msgid "server" msgstr "" #: library/cgi.rst:389 library/cgi.rst:462 msgid "CGI" msgstr "" #: library/cgi.rst:10 msgid "protocol" msgstr "" #: library/cgi.rst:10 msgid "HTTP" msgstr "" #: library/cgi.rst:10 msgid "MIME" msgstr "" #: library/cgi.rst:10 msgid "headers" msgstr "" #: library/cgi.rst:10 msgid "URL" msgstr "" #: library/cgi.rst:10 msgid "Common Gateway Interface" msgstr "" #: library/cgi.rst:389 msgid "security" msgstr "" #: library/cgi.rst:462 msgid "debugging" msgstr ""