Well I fixed this using a ISAPI filter which I will release soon (once I
have some time) that takes a url /a/b/c/x.pcgi/f/g/h, and passes
/a/b/c/x.pcgi to IIS so the file will run and /f/g/h to Zope.
My next question is has anyone succeeded in getting this to work to another
box over a mapped or shared win32 drive?
I mapped g:\ to my zope host, and then specified
PCGI_PUBLISHER=g:\pcgi\pcgi_publisher.py in my pcgi file. The problem seems
to pcgi-wrapper.exe which does not like a mapped drive. (line 485 of
parseinfo.c keeps spitting out missing publisher)...
Thanks in advance and apologies for the cross post to zope-dev but it is
more of a zope-dev question.
----- Original Message -----
From: "Andy McKay" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 17, 2000 1:33 PM
Subject: [Zope] IIS and PCGI
> Im fiddling with IIS and PCGI, I've looked at
> (http://www.zope.org/Members/brianh/iis_howto) the docs and got the server
> to work correctly in that http://127.0.0.1/zope.pcgi is the same as
> However it doesnt seem to be carrying through the trailing path info (or /
> 's) for example
> http://127.0.0.1/zope.pcgi/manage brings up 404. Using IIS 5.0, Win2k,
> Anyone encountered this and know the solution?
> Andy McKay, Developer.
> Zope maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope-dev )
Zope maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -