1.1 --- a/README.txt Wed Aug 24 21:33:22 2005 +0000
1.2 +++ b/README.txt Wed Aug 24 21:35:54 2005 +0000
1.3 @@ -45,10 +45,10 @@
1.4
1.5 BaseHTTPRequestHandler Python 2.2.2, Python 2.3.3, Python 2.4.1
1.6 CGI Apache 2.0.44, Apache 2.0.53, AOLserver 4.0.10, lighttpd 1.3.15
1.7 -Jython/Java Servlet API Jython 2.1, Java JDK 1.3.1_02, Tomcat 4.1.27 (Servlet 2.3)
1.8 +Jython/Java Servlet API Jython 2.1, Java JDK 1.3.1_02, Tomcat 4.1.31 (Servlet 2.3)
1.9 mod_python 3.0.3 (3.1.3 for framework cookie and session support)
1.10 Twisted 1.0.5, 1.3.0
1.11 -Webware 0.8.1, CVS (2004-02-06)
1.12 +Webware 0.8.1, CVS (2004-02-06), 0.9b2
1.13 WSGI run_with_cgi (PEP 333)
1.14 Zope 2.7.2-0, 2.8.0-final
1.15
1.16 @@ -195,7 +195,13 @@
1.17 Interpretation of path field encodings needs to be verified. Currently,
1.18 stray path fields are handled (eg. in WebStack.Helpers.Request) as being
1.19 ISO-8859-1, but it might be the case that some such fields might be
1.20 -submitted as UTF-8.
1.21 +submitted as UTF-8. The decode_path method on Transaction does do much of the
1.22 +work that is likely to be required, however.
1.23 +
1.24 +An interesting test of encodings is to introduce things like the following to
1.25 +the path info and query string sections of the URL: %25F0?%E6=%F8&%25F0=%F8
1.26 +This should produce the following decoded result: %F0?æ=ø&%F0=ø
1.27 +(The above needs to be read in ISO-8859-1 or ISO-8859-15.)
1.28
1.29 Cookie objects need defining strictly, especially since the standard library
1.30 Cookie object behaves differently to mod_python (and possibly Webware)
1.31 @@ -228,7 +234,7 @@
1.32
1.33 Investigate proper support for HEAD, OPTIONS and other request methods.
1.34
1.35 -Consider packages for different operating systems.
1.36 +Consider packages for different operating systems (other than Debian).
1.37
1.38 (Completed/rejected)
1.39