NOTE: If you are a developer, please use a private wiki based on foswiki/trunk on a daily base ...or use
trunk.foswiki.org to view this page for some minimal testing.
Use
Item9693 for docu changes for 1.2 and 2.0.
Item908: adding a script suffix seems to confuse the url parsing code
| Priority: |
CurrentState: |
AppliesTo: |
Component: |
WaitingFor: |
| Urgent |
Closed |
Engine |
|
|
if you add
.pl and goto
http://yourfoswiki/bin/view.pl the parsing code will tell you it can't fine the
Pl topic
will be a pretty trivial unit test to add and then fix - related to the other bug fix i did in this area, and the feature proposal Kenneth kindly made me
--
SvenDowideit - 29 Jan 2009
Foswiki core expects
PATH_INFO to be something like
/Web/Subweb/Topic. IIS adjusts it to
/foswiki/bin/view.pl/Web/Subweb/Topic.
Foswiki::Engine::CGI::preparePath() already handle this case:
# SMELL: "The Microsoft Internet Information Server is broken with
# respect to additional path information. If you use the Perl DLL
# library, the IIS server will attempt to execute the additional
# path information as a Perl script. If you use the ordinary file
# associations mapping, the path information will be present in the
# environment, but incorrect. The best thing to do is to avoid using
# additional path information."
# (...)
my $cgiScriptPath = $ENV{SCRIPT_NAME};
$pathInfo =~ s{$cgiScriptPath/}{/}i;
This workaround works to
/foswiki/bin/view.pl/ but not to
/foswiki/bin/view.pl (notice the trailing slash).
So this workaround should be improved.
--
GilmarSantosJr - 30 Jan 2009