-
-
Notifications
You must be signed in to change notification settings - Fork 261
Expand file tree
/
Copy pathcgi.po
More file actions
659 lines (567 loc) · 24.5 KB
/
cgi.po
File metadata and controls
659 lines (567 loc) · 24.5 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
# Copyright (C) 2001-2018, Python Software Foundation
# For licence information, see README file.
#
msgid ""
msgstr ""
"Project-Id-Version: Python 3.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-06-28 15:29+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: FRENCH <traductions@lists.afpy.org>\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../Doc/library/cgi.rst:2
msgid ":mod:`cgi` --- Common Gateway Interface support"
msgstr ""
#: ../Doc/library/cgi.rst:7
msgid "**Source code:** :source:`Lib/cgi.py`"
msgstr "**Code source :** :source:`Lib/cgi.py`"
#: ../Doc/library/cgi.rst:19
msgid "Support module for Common Gateway Interface (CGI) scripts."
msgstr ""
#: ../Doc/library/cgi.rst:21
msgid ""
"This module defines a number of utilities for use by CGI scripts written in "
"Python."
msgstr ""
#: ../Doc/library/cgi.rst:26
msgid "Introduction"
msgstr "Introduction"
#: ../Doc/library/cgi.rst:30
msgid ""
"A CGI script is invoked by an HTTP server, usually to process user input "
"submitted through an HTML ``<FORM>`` or ``<ISINDEX>`` element."
msgstr ""
#: ../Doc/library/cgi.rst:33
msgid ""
"Most often, CGI scripts live in the server's special :file:`cgi-bin` "
"directory. The HTTP server places all sorts of information about the request "
"(such as the client's hostname, the requested URL, the query string, and "
"lots of other goodies) in the script's shell environment, executes the "
"script, and sends the script's output back to the client."
msgstr ""
#: ../Doc/library/cgi.rst:39
msgid ""
"The script's input is connected to the client too, and sometimes the form "
"data is read this way; at other times the form data is passed via the "
"\"query string\" part of the URL. This module is intended to take care of "
"the different cases and provide a simpler interface to the Python script. "
"It also provides a number of utilities that help in debugging scripts, and "
"the latest addition is support for file uploads from a form (if your browser "
"supports it)."
msgstr ""
#: ../Doc/library/cgi.rst:46
msgid ""
"The output of a CGI script should consist of two sections, separated by a "
"blank line. The first section contains a number of headers, telling the "
"client what kind of data is following. Python code to generate a minimal "
"header section looks like this::"
msgstr ""
#: ../Doc/library/cgi.rst:54
msgid ""
"The second section is usually HTML, which allows the client software to "
"display nicely formatted text with header, in-line images, etc. Here's "
"Python code that prints a simple piece of HTML::"
msgstr ""
#: ../Doc/library/cgi.rst:66
msgid "Using the cgi module"
msgstr ""
#: ../Doc/library/cgi.rst:68
msgid "Begin by writing ``import cgi``."
msgstr ""
#: ../Doc/library/cgi.rst:70
msgid "When you write a new script, consider adding these lines::"
msgstr ""
#: ../Doc/library/cgi.rst:75
msgid ""
"This activates a special exception handler that will display detailed "
"reports in the Web browser if any errors occur. If you'd rather not show "
"the guts of your program to users of your script, you can have the reports "
"saved to files instead, with code like this::"
msgstr ""
#: ../Doc/library/cgi.rst:83
msgid ""
"It's very helpful to use this feature during script development. The reports "
"produced by :mod:`cgitb` provide information that can save you a lot of time "
"in tracking down bugs. You can always remove the ``cgitb`` line later when "
"you have tested your script and are confident that it works correctly."
msgstr ""
#: ../Doc/library/cgi.rst:88
msgid ""
"To get at submitted form data, use the :class:`FieldStorage` class. If the "
"form contains non-ASCII characters, use the *encoding* keyword parameter set "
"to the value of the encoding defined for the document. It is usually "
"contained in the META tag in the HEAD section of the HTML document or by "
"the :mailheader:`Content-Type` header). This reads the form contents from "
"the standard input or the environment (depending on the value of various "
"environment variables set according to the CGI standard). Since it may "
"consume standard input, it should be instantiated only once."
msgstr ""
#: ../Doc/library/cgi.rst:97
msgid ""
"The :class:`FieldStorage` instance can be indexed like a Python dictionary. "
"It allows membership testing with the :keyword:`in` operator, and also "
"supports the standard dictionary method :meth:`~dict.keys` and the built-in "
"function :func:`len`. Form fields containing empty strings are ignored and "
"do not appear in the dictionary; to keep such values, provide a true value "
"for the optional *keep_blank_values* keyword parameter when creating the :"
"class:`FieldStorage` instance."
msgstr ""
#: ../Doc/library/cgi.rst:105
msgid ""
"For instance, the following code (which assumes that the :mailheader:"
"`Content-Type` header and blank line have already been printed) checks that "
"the fields ``name`` and ``addr`` are both set to a non-empty string::"
msgstr ""
#: ../Doc/library/cgi.rst:119
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 ""
#: ../Doc/library/cgi.rst:126
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 ""
#: ../Doc/library/cgi.rst:139
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 ""
#: ../Doc/library/cgi.rst:159
msgid ""
":class:`FieldStorage` objects also support being used in a :keyword:`with` "
"statement, which will automatically close them when done."
msgstr ""
#: ../Doc/library/cgi.rst:162
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 ""
#: ../Doc/library/cgi.rst:167
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 ""
#: ../Doc/library/cgi.rst:175
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 ""
#: ../Doc/library/cgi.rst:180
msgid ""
"A form submitted via POST that also has a query string will contain both :"
"class:`FieldStorage` and :class:`MiniFieldStorage` items."
msgstr ""
#: ../Doc/library/cgi.rst:183
msgid ""
"The :attr:`~FieldStorage.file` attribute is automatically closed upon the "
"garbage collection of the creating :class:`FieldStorage` instance."
msgstr ""
#: ../Doc/library/cgi.rst:187
msgid ""
"Added support for the context management protocol to the :class:"
"`FieldStorage` class."
msgstr ""
#: ../Doc/library/cgi.rst:193
msgid "Higher Level Interface"
msgstr ""
#: ../Doc/library/cgi.rst:195
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 ""
#: ../Doc/library/cgi.rst:204
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 ""
#: ../Doc/library/cgi.rst:208
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 ""
#: ../Doc/library/cgi.rst:217
msgid ""
"This situation is common for example when a form contains a group of "
"multiple checkboxes with the same name::"
msgstr ""
#: ../Doc/library/cgi.rst:223
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 ""
#: ../Doc/library/cgi.rst:229
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 ""
#: ../Doc/library/cgi.rst:237
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 ""
#: ../Doc/library/cgi.rst:241
msgid ""
"A more convenient approach is to use the methods :meth:`~FieldStorage."
"getfirst` and :meth:`~FieldStorage.getlist` provided by this higher level "
"interface."
msgstr ""
#: ../Doc/library/cgi.rst:247
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 ""
#: ../Doc/library/cgi.rst:258
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 ""
#: ../Doc/library/cgi.rst:262
msgid "Using these methods you can write nice compact code::"
msgstr ""
#: ../Doc/library/cgi.rst:274
msgid "Functions"
msgstr "Fonctions"
#: ../Doc/library/cgi.rst:276
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 ""
#: ../Doc/library/cgi.rst:282
msgid ""
"Parse a query in the environment or from a file (the file defaults to ``sys."
"stdin``). The *keep_blank_values* and *strict_parsing* parameters are "
"passed to :func:`urllib.parse.parse_qs` unchanged."
msgstr ""
#: ../Doc/library/cgi.rst:289
msgid ""
"This function is deprecated in this module. Use :func:`urllib.parse."
"parse_qs` instead. It is maintained here only for backward compatibility."
msgstr ""
#: ../Doc/library/cgi.rst:295
msgid ""
"This function is deprecated in this module. Use :func:`urllib.parse."
"parse_qsl` instead. It is maintained here only for backward compatibility."
msgstr ""
#: ../Doc/library/cgi.rst:301
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 ""
#: ../Doc/library/cgi.rst:306
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 ""
#: ../Doc/library/cgi.rst:310
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 ""
#: ../Doc/library/cgi.rst:314
msgid ""
"Added the *encoding* and *errors* parameters. For non-file fields, the "
"value is now a list of strings, not bytes."
msgstr ""
#: ../Doc/library/cgi.rst:321
msgid ""
"Parse a MIME header (such as :mailheader:`Content-Type`) into a main value "
"and a dictionary of parameters."
msgstr ""
#: ../Doc/library/cgi.rst:327
msgid ""
"Robust test CGI script, usable as main program. Writes minimal HTTP headers "
"and formats all information provided to the script in HTML form."
msgstr ""
#: ../Doc/library/cgi.rst:333
msgid "Format the shell environment in HTML."
msgstr ""
#: ../Doc/library/cgi.rst:338
msgid "Format a form in HTML."
msgstr ""
#: ../Doc/library/cgi.rst:343
msgid "Format the current directory in HTML."
msgstr ""
#: ../Doc/library/cgi.rst:348
msgid "Print a list of useful (used by CGI) environment variables in HTML."
msgstr ""
#: ../Doc/library/cgi.rst:353
msgid ""
"Convert the characters ``'&'``, ``'<'`` and ``'>'`` in string *s* to HTML-"
"safe sequences. Use this if you need to display text that might contain "
"such characters in HTML. If the optional flag *quote* is true, the "
"quotation mark character (``\"``) is also translated; this helps for "
"inclusion in an HTML attribute value delimited by double quotes, as in ``<a "
"href=\"...\">``. Note that single quotes are never translated."
msgstr ""
#: ../Doc/library/cgi.rst:360
msgid ""
"This function is unsafe because *quote* is false by default, and therefore "
"deprecated. Use :func:`html.escape` instead."
msgstr ""
#: ../Doc/library/cgi.rst:368
msgid "Caring about security"
msgstr ""
#: ../Doc/library/cgi.rst:372
msgid ""
"There's one important rule: if you invoke an external program (via the :func:"
"`os.system` or :func:`os.popen` functions. or others 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 ""
#: ../Doc/library/cgi.rst:380
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 ""
#: ../Doc/library/cgi.rst:386
msgid "Installing your CGI script on a Unix system"
msgstr ""
#: ../Doc/library/cgi.rst:388
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 ""
#: ../Doc/library/cgi.rst:392
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 ""
#: ../Doc/library/cgi.rst:399
msgid ""
"Make sure the Python interpreter exists and is executable by \"others\"."
msgstr ""
#: ../Doc/library/cgi.rst:401
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 ""
#: ../Doc/library/cgi.rst:412
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 ""
#: ../Doc/library/cgi.rst:420
msgid "(This way, the directory inserted last will be searched first!)"
msgstr ""
#: ../Doc/library/cgi.rst:422
msgid ""
"Instructions for non-Unix systems will vary; check your HTTP server's "
"documentation (it will usually have a section on CGI scripts)."
msgstr ""
#: ../Doc/library/cgi.rst:427
msgid "Testing your CGI script"
msgstr ""
#: ../Doc/library/cgi.rst:429
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 ""
#: ../Doc/library/cgi.rst:436
msgid ""
"Assuming your script has no syntax errors, yet it does not work, you have no "
"choice but to read the next section."
msgstr ""
#: ../Doc/library/cgi.rst:441
msgid "Debugging CGI scripts"
msgstr ""
#: ../Doc/library/cgi.rst:445
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 form. 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 ""
#: ../Doc/library/cgi.rst:458
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 ""
#: ../Doc/library/cgi.rst:467
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 ""
#: ../Doc/library/cgi.rst:472
msgid ""
"This should produce the same results as those gotten from installing the :"
"file:`cgi.py` file itself."
msgstr ""
#: ../Doc/library/cgi.rst:475
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 ""
#: ../Doc/library/cgi.rst:482
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 ""
#: ../Doc/library/cgi.rst:489
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 ""
#: ../Doc/library/cgi.rst:493
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 ""
#: ../Doc/library/cgi.rst:502
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 ""
#: ../Doc/library/cgi.rst:511
msgid "Common problems and solutions"
msgstr ""
#: ../Doc/library/cgi.rst:513
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 ""
#: ../Doc/library/cgi.rst:517
msgid "Check the installation instructions above."
msgstr ""
#: ../Doc/library/cgi.rst:519
msgid ""
"Check the HTTP server's log files. (``tail -f logfile`` in a separate "
"window may be useful!)"
msgstr ""
#: ../Doc/library/cgi.rst:522
msgid ""
"Always check a script for syntax errors first, by doing something like "
"``python script.py``."
msgstr ""
#: ../Doc/library/cgi.rst:525
msgid ""
"If your script does not have any syntax errors, try adding ``import cgitb; "
"cgitb.enable()`` to the top of the script."
msgstr ""
#: ../Doc/library/cgi.rst:528
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 ""
#: ../Doc/library/cgi.rst:532
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 ""
#: ../Doc/library/cgi.rst:537
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 ""
#: ../Doc/library/cgi.rst:541
msgid "Footnotes"
msgstr "Notes"
#: ../Doc/library/cgi.rst:542
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 ""