We have a (slightly modified) version of Betsie
running on a site we host. It's been running for
quite a while, and we have not had any complaints.
Recently, however, some changes have happened to our
servers. Patches etc. I don't know the exact details
of all of them (only a lowly developer).
However, now Betsie seems to be playing up. Well, not
Betsie, but the way Betsie uses the querystring.
Basically, parser.pl opens fine, and will default
correctly to the home page. However, the links (in
the form
of "parser.pl/0005/www.example.co.uk/home.htm") are
not being understood. IIS returns a 404 error.
As far as I can tell, IIS is not making a request to
parser.pl. It is taking /0005/... as still part of
the directory name.
Anyone had the same problem, especially if it involved
any of the recent IIS 5 patches?
Tearing my hair out at the moment - there doesn't seem
to be any way of forcing IIS to do anything!
Help please!
Craig.
Logged In: NO
Did you solve this problem? Im getting similar results.
Using ? after the scrupt name isn't helping either.
Rich
Logged In: NO
I also have this problem now, for a customers site. Anyone
have any news ?
Logged In: YES
user_id=520498
Has anyone had luck with this problem? We are trying to
get Betsie to work on our system. It interprets the first
page fine, but any links on the page won't work.
Logged In: YES
user_id=169665
This is an IIS issue. IIS does not properly support the CGI
standard. Perhaps you could take the issue up with the
vendor.
Logged In: YES
user_id=531427
Given a) MS aren't going to care too much how perl performs
after patch installations b) perl programmers have, how can
we put it, no real history of being concerned how their
code may work on IIS (why should they after all) and c)
perl on IIS is a square peg in a round whole anyway..
Just write one in ASP! I did!
Probably like yourself I have little time for side projects
but it didn't take long to knock up a roughly working
version.. when I get the chance to put some polish on it,
I'll let you know. Like Betsie, it'd be good if
accessibility empowering code is free.
Logged In: YES
user_id=591717
Possible solution to IIS5 & Win 2000 Betsie compatibility issues: Querystring not being understood / 404-page not
found error / BETSIE will not work in general.
Having followed all default installation instructions given for an ActivePerl installation on IIS5 and BETSIE with Win
2000, we were experiencing many of the problems expressed in the
Sourceforge ( http://sourceforge.net/tracker/index.php?func=detail&aid=437856&group_id=22386&atid=376185 )
and
Geocrawler ( http://www.geocrawler.com/archives/3/11309/2002/6/0/9013019/ ) forums.
However we have have found a solution to our setup. We discovered when disabling the "Check file exists"
checkbox for our .pl files BETSIE worked!
http://www.nwifhe.ac.uk/cgi-bin/betsie/parser.pl/www.nwifhe.ac.uk
To do this:
1. Open ISM and right-click the default directory,
2. Go to "Home Directory" panel.
3. Click "Congifuration" and select the perl file extension (.pl in our case). This may be .cgi for others.
4. Click "Edit" and uncheck "Check file exists" box. Then "Apply" and "OK".
Make sure that you have followed the enabling PATH_INFO instruction links given in the BETSIE readme:
- http://support.microsoft.com/default.aspx?scid=kb;EN-US;q184320
- http://msdn.microsoft.com/library/psdk/iisref/apro8mr7.htm
Hopefully this will work for you irritated BETSIE-IIS5-Win 2000 people out there?
Regards,
Keith Smith (MIS) & James Keegan (WebDeveloper)
NWIFHE.