Python CGI checklist: Difference between revisions

From XPUB & Lens-Based wiki
m (Michael Murtaugh moved page CGI checklist to Python CGI checklist over redirect)
 
(4 intermediate revisions by 2 users not shown)
Line 30: Line 30:
   chmod 755 myscript.cgi
   chmod 755 myscript.cgi


== Print the Content-type ==
== Print the Content-type first! ==


The '''first output''' of your script must be the "HTTP headers", which at the very least should be a Content-type (with optional character set) '''followed by a blank line''' (which terminates the headers section). After that, all output is considered the "contents" of the document.
The '''first output''' of your script must be the "HTTP headers", which at the very least should be a Content-type (with optional character set) '''followed by a blank line''' (which terminates the headers section). After that, all output is considered the "contents" of the document.
Line 40: Line 40:


== Troubleshooting ==
== Troubleshooting ==
=== Make sure you're view the script through HTTP / a web server ===
=== Make sure you are viewing the script through HTTP / a web server (and not as a local file) ===


If you're seeing the actual source code of the script, you need to make sure that you are viewing the script via a webserver (not just opening the script directly as a file). In other words, the URL should start with "http:" not "file:".
It's the web server that actually performs a CGI script -- not the browser, so make sure you're looking at the script ''via a webserver'' rather than directly opening the script in your browser. (This would be one reason you might be seeing the raw source code of the script rather than it's output). In any case the URL (in the browser) should start with "http:" not "file:".


  http://localhost/cgi-bin/script.cgi
  http://localhost/cgi-bin/script.cgi
Line 51: Line 51:
  file:///this/can't/be/right/script.cgi
  file:///this/can't/be/right/script.cgi


And if this doesn't work, make sure your webserver is running (Debian: /etc/init.d/apache2 restart... Mac OS X: System Preferences, Sharing, Personal Web Sharing should be switched on).
See [[Serve.py]] for a tip on how to run a simple local CGI-capable webserver with a simple python command.


=== Display python errors in the browser ===
=== Display python errors in the browser ===
Line 64: Line 64:
Use a shell on the server machine (so ssh to pzwart if that's where you're running) and:
Use a shell on the server machine (so ssh to pzwart if that's where you're running) and:


  tail /var/log/apache2/error_log
  tail /var/log/apache2/error.log

Latest revision as of 11:34, 12 February 2014

InternalServerErrorNegate.png

"Internal server error" got you down... no problem, just check the following

Use extension ".cgi"

The default extension for CGI on a web server is .cgi.

She-Bang!

The very first line of the file should be the "shebang" telling the system (Apache) how to run the script (in other words which language it is).

#!/usr/bin/python

Even better, you could use the "env" trick (finds whatever python is available) + also specify a text encoding while you're at it (in case your code has special characters in it)

#!/usr/bin/env python
#-*- coding:utf-8 -*-

chmod +x

Permissions must be set to "world-executable". You can maybe set this via an (s)ftp program, but the simplest / most failsafe way is directly via the shell:

 chmod +x myscript.cgi

or

 chmod 755 myscript.cgi

Print the Content-type first!

The first output of your script must be the "HTTP headers", which at the very least should be a Content-type (with optional character set) followed by a blank line (which terminates the headers section). After that, all output is considered the "contents" of the document.

print "Content-type: text/html;charset=utf-8"
print

Troubleshooting

Make sure you are viewing the script through HTTP / a web server (and not as a local file)

It's the web server that actually performs a CGI script -- not the browser, so make sure you're looking at the script via a webserver rather than directly opening the script in your browser. (This would be one reason you might be seeing the raw source code of the script rather than it's output). In any case the URL (in the browser) should start with "http:" not "file:".

http://localhost/cgi-bin/script.cgi
http://pzwart3.wdka.hro.nl/~YOU/cgi-bin/script.cgi

not

file:///this/can't/be/right/script.cgi

See Serve.py for a tip on how to run a simple local CGI-capable webserver with a simple python command.

Display python errors in the browser

Once the script is actually running, there might of course be something wrong in the code of the program itself. By default, if a python exception occurs, you will see either an Internal Server Error or (worse) a blank page. The cgitb module (CGI Trackback) will make python errors appear, and even formats them for a browser.

import cgitb; cgitb.enable()

Check the webserver's error log

Use a shell on the server machine (so ssh to pzwart if that's where you're running) and:

tail /var/log/apache2/error.log