You can subscribe to this list here.
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
---|
From: Blum, J. <jon...@or...> - 2012-12-07 14:21:41
|
Hello all -- I'm afraid I'm in a bit of a bind. I'm working on a major web platform which has to go live in just about a week... and just a few days ago, an incompatibility meant we had to move part of our site from Apache to IIS. So now I've suddenly got to integrate Webcullis in front of Perl scripts on IIS 7.5. This is proving surprisingly complicated -- while the rest of the site is protected just fine, we're having difficulties with the ActivePerl scripts. If I install Webcullis according to the PDF addendum, running a script actually crashes the web process (apparently an unhandled exception). If I leave out the IIS7 Webcullis DLL and return to the ISAPI configuration of previous versions... Webcullis appears to be functioning normally, but the Perl scripts are not actually blocked by Webcullis' rules. No matter what the script, or what directory it's in. I've tried making sure that the Webcullis handler module is higher in the IIS food chain than the Perl ISAPI handler... doesn't seem to make a difference. Anyone out there got insights on combining Webcullis with ActivePerl under IIS7, who would be able to help me out over the next few (rather intense) days? Cheers, Jon Blum |