[issue5340] Change in cgi behavior breaks existing software

Change by Inada Naoki : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue5340] Change in cgi behavior breaks existing software

Changes by Éric Araujo mer...@netwok.org: -- versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5340 ___ ___ Python-bugs-list

[issue5340] Change in cgi behavior breaks existing software

Changes by Facundo Batista facu...@taniquetil.com.ar: -- assignee: facundobatista - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5340 ___ ___

[issue5340] Change in cgi behavior breaks existing software

Bob Kline bkl...@rksystems.com added the comment: Just to make life interesting, someone went in and changed all the URLs for messages in the Python mailing list. Here's the new URL for the message which contains the repro instructions:

[issue5340] Change in cgi behavior breaks existing software

Changes by Georg Brandl ge...@python.org: -- assignee: - facundobatista nosy: +facundobatista ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5340 ___

[issue5340] Change in cgi behavior breaks existing software

New submission from Bob Kline bkl...@rksystems.com: We just upgraded Python to 2.6 on some of our servers and a number of our CGI scripts broke because the cgi module has changed the way it handles POST requests. When the 'action' attribute was not present in the form element on an HTML page

[issue5340] Change in cgi behavior breaks existing software

Paul Boddie p...@boddie.org.uk added the comment: The issue of distinguishing between query-originating parameters and form-originating parameters has been around for a very long time, and in my own work, especially where the cgi module has been used, I've been careful to distinguish between the