[Moin-devel] Re: 1.3.2 does not run on IIS due to error in request.py

[Alexander Schremmer]

On Mon, 24 Jan 2005 17:24:42 +0100, Alexander Schremmer wrote:

>> In request.py, function RequestBase::_setup_vars_from_std_env there is some
>> special code to handle some strange stuff on windows.

Yeah, it is even new in 1.3.2.

>> The first branch is supposed to be checking for apache and if this fails,
>> the second branch is checking for IIS.

The first branch is just used if the server supplies request_uri. IIS does
not, so it will be relevant if the CGI is just executed on IIS.

If the first branch was not used, the second checks if IIS called the CGI
script. If this is true, it tries to decode the path_info.

>> However the second branch is never executed due to an obvious error in the
>> first check:

I still do not think that this is an error.

>> The symptoms of this error were not easy to understand, because most of the
>> unit tests (I re-enabled them) worked OK and I could perfectly work with
>> FrontPage - but only with FrontPage! Whichever page was requested I always
>> got just FrontPage.

Funnily, this should be the consequence after applying your hints :-)

I have installed IIS just because I wanted to make sure that my addition in
request.py was correct. Besides a minor error that disallowes the page view
of pages containing characters that cannot be displayed in the system code
page (e.g. Asian ones), it was perfectly valid and worked without any
further problems on IIS 5.1.

A little fix for that glitch will be in the hotfix release that
ThomasWaldmann will finish in the next hours.

Maybe you should check in your configuration if you enabled "Check that
file exists". This may not be enabled because IIS would check if the
(virtual) page name exists in the directory script.

If this still does not fix your problem, you should try to contact my
personally.

Kind regards,
Alexander