# HG changeset patch # User paulb # Date 1124919354 0 # Node ID cf6356dbde7607e7260a83668fbfdaa0434e2254 # Parent ef07fa642f025fc4d01f4d9109ce1658c325f2fa [project @ 2005-08-24 21:35:54 by paulb] Updated release information and added testing notes about paths, parameters and encodings. diff -r ef07fa642f02 -r cf6356dbde76 README.txt --- a/README.txt Wed Aug 24 21:33:22 2005 +0000 +++ b/README.txt Wed Aug 24 21:35:54 2005 +0000 @@ -45,10 +45,10 @@ BaseHTTPRequestHandler Python 2.2.2, Python 2.3.3, Python 2.4.1 CGI Apache 2.0.44, Apache 2.0.53, AOLserver 4.0.10, lighttpd 1.3.15 -Jython/Java Servlet API Jython 2.1, Java JDK 1.3.1_02, Tomcat 4.1.27 (Servlet 2.3) +Jython/Java Servlet API Jython 2.1, Java JDK 1.3.1_02, Tomcat 4.1.31 (Servlet 2.3) mod_python 3.0.3 (3.1.3 for framework cookie and session support) Twisted 1.0.5, 1.3.0 -Webware 0.8.1, CVS (2004-02-06) +Webware 0.8.1, CVS (2004-02-06), 0.9b2 WSGI run_with_cgi (PEP 333) Zope 2.7.2-0, 2.8.0-final @@ -195,7 +195,13 @@ Interpretation of path field encodings needs to be verified. Currently, stray path fields are handled (eg. in WebStack.Helpers.Request) as being ISO-8859-1, but it might be the case that some such fields might be -submitted as UTF-8. +submitted as UTF-8. The decode_path method on Transaction does do much of the +work that is likely to be required, however. + +An interesting test of encodings is to introduce things like the following to +the path info and query string sections of the URL: %25F0?%E6=%F8&%25F0=%F8 +This should produce the following decoded result: %F0?æ=ø&%F0=ø +(The above needs to be read in ISO-8859-1 or ISO-8859-15.) Cookie objects need defining strictly, especially since the standard library Cookie object behaves differently to mod_python (and possibly Webware) @@ -228,7 +234,7 @@ Investigate proper support for HEAD, OPTIONS and other request methods. -Consider packages for different operating systems. +Consider packages for different operating systems (other than Debian). (Completed/rejected)