= Description = The mod_py class in request.py gets an unquoted representation of the script name. I dont know if this is correct, at least it's different than in other servers. This breaks many things if you deal with page names that use unicode characters. == Steps to reproduce == Here is a wiki where you can see the contents of request.script_name (sp?) after it is read from the environment at the top: [[http://wiki.cs.huji.ac.il/%d7%a9%d7%99%d7%a0%d7%95%d7%99%d7%99%d7%9d_%d7%90%d7%97%d7%a8%d7%95%d7%a0%d7%99%d7%9d|RecentChanges (he) in a mod_py driven wiki]] == Details == || '''!MoinMoin Version''' || 1.3.1 || || '''Server Setup''' || Apache/mod_py || == Workaround == ## How to deal with the bug until it is fixed None known. = Discussion = I can't reproduce the problem with both 1.3.1 and 1.3.2 dev on Mac OS X and Apache 1.3. --NirSoffer According to the RFC, the variable may not be url-encoded. IMHO this looks like a bug in our code. * Reference? See the CGI/1.1 RFC. Why the we don't see this problem with other servers? The problem is that the wrapper has to fill script name and path info somehow. His mod_python fills the script_name with the pagename which is obviously wrong but may not fail like this. So just rename your scripts and you should see the problem as well. I see mod_python setting the script name as the pagename (and the page_info to nothing) if you attempt to make moin run at the root of a website. When you select a further page from the wiki you then get script name set to the first page you visited and page_info set to the current page. I have not found a workround for this with moin 1.3.1. -- NigelMetheringham <> There is no problem to run as root, just use proper config, see HelpOnConfiguration/ApacheVoodoo. This is only a side effect when modpy config is broken, and not a real problem. Nobody use non-ascii script names, so nobody has this problem. When we want to support non-ascii scriptnames, we will decode them properly. Closing this bug, not a real problem. This bug exists for standard installs. We have to fix the docs or workaround the problem or find the problem in the modpy request class. Can you describe the steps to reproduce this bug using standard install? = Plan = ## This part is for Moin``Moin developers: * Priority: * Assigned to: * Status: Duplicate of ../ScriptNameHasToBeAnOption ---- ## When the bug is fixed, replace the category to Category MoinMoinBugFixed ## If this is not a bug, replace with Category MoinMoinNoBug CategoryMoinMoinBugFixed [[CategoryRelease1.3.5]]