Re: Re: Re: #exec in SSI

Not that I know much about web servers, etc., but a Google search led me to think that HSE_STATUS_PENDING is a response associated with ISAPI, rather than CGI.

You've probably looked at all this, but IIS configs for scripts as CGI vs scripts for ISAPI seem to be addressed at various places:

Could it be that an additional or corrected IIS config would bypass the need to programmatically send this flag?

Comment on Re: Re: Re: #exec in SSI

Replies are listed 'Best First'.
Re: Re: Re: Re: #exec in SSI by jimac (Initiate) on May 08, 2002 at 15:11 UTC
You may be right, and I found the same references to ISAPI (specifically, how to handle HSE_STATUS_PENDING in ASP). However, the SSI #exec makes a distinction between executing via CGI and EXE, so I assume that it will handle CGI. It may well be that it is not possible to #exec a perl cgi program under IIS. I have only been playing around with this and I haven't had a lot of time to investigate it in detail (I was just hoping somebody here might have come across it before). I'm going to play around a bit more and see if I can come up with something. If I find a solution, I'll post something here ;-) Jim.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: #exec in SSI
by jimac (Initiate) on May 08, 2002 at 15:11 UTC

However, the SSI #exec makes a distinction between executing via CGI and EXE, so I assume that it will handle CGI.

It may well be that it is not possible to #exec a perl cgi program under IIS. I have only been playing around with this and I haven't had a lot of time to investigate it in detail (I was just hoping somebody here might have come across it before).

I'm going to play around a bit more and see if I can come up with something.

If I find a solution, I'll post something here ;-)

Jim.

[reply]