Menu
▾
▴
#24 Static and dynamic content cannot be "rehomed" correctly
There are many hard-coded paths and incorrect use of URI creation, etc. so one cannot correctly "rehome" the static and dynamic content to a different URI path and/or a different HTTP port, etc. This at least affects common/localdefs.py and everything that depends upon it.
Some key examples are:
the inclusion of "cgi-bin" strewn all over the code
the way HTFAKE (what is that even supposed to mean?) is used in the code where it is always joined to "http:/" and starts with "/"; In URI definition the "//" are logically a single thing and this sort of usage is not useful (one can change the domain hosted on but not much else).
the way COOKIEHOST is unused but HTMLHOST host is used in HTTP cookie contexts. There is no way to correctly host on a port other than 80 as the port should not be included in the cookie domain or logins fail.
Discussion
Anonymous
Work on this should refer to RFC 3986 (the current generic URI standard).
Work on this should probably also refer to RFC 3875 (CGI) and PEP 333 (WSGI 1.1) as these define things like SCRIPT_NAME, PATH_INFO, QUERY_STRING, etc.
Ticket moved from /p/isfdb/bugs/207/