I think I have found a rather specific bug, and I was wondering if anyone else has encountered this (I'm hoping you have).

I've recently setup an old Perl CGI application to run under FastCGI using a dispatcher script. I've gotten this application to run in both Windows (IIS) and Linux (Apache), and for the most part it runs very stably except for one important exception.

On Windows, using IIS 7 and its FastCGI extension, my FastCGI Perl process dies every time it receives a POST. I've traced the death to FCGI and specifically the libfcgi code that it uses.

In fcgiapp.c, at about line 1717, there is code to close the stream when an empty "FastCGI Packet" is received. After reading the FastCGI Specification's (http://www.fastcgi.com/devkit/doc/fcgi-spec.html) examples at the bottom, I can see that every incoming FastCGI request should end with an empty packet of its own type when it is a FCGI_PARAMS packet or a FCGI_STDIN package. The code in fcgiapp.c seems to close the stream when either an empty FCGI_PARAMS or FCGI_STDIN packet is received, and does not expect any further packets.

Now on Apache, this doesn't seem to cause a problem. On IIS though, when receiving a POST, it sends a FCGI_STDIN packet after an empty FCGI_PARAMS packet. The server, having already seen the empty FCGI_PARAMS packet, seems to close the connection before receiving the FCGI_STDIN packet properly.

I find it hard to believe that a bug like this could have been around so long without someone noticing. That is why I feel this is either a configuration issue, or a problem with my code. If there are others who have experienced this though, I can try to find a common pattern.

Thanks for your time, monks. I hope this discussion ends with a stronger FCGI.pm module, or less buggy version of my code.

The following are links to IIS.net posts about similar problems but with different languages being used:

http://forums.iis.net/t/1170379.aspx
http://forums.iis.net/t/1150498.aspx

Update:I found a solution that works, but unfortunately I don't think it can be fully trusted. I added another action to the FillBuffProc switch statement, and called it PASS_RECORD. Unlike SKIP, it only ignores the current packet, and not the next one as well. I then changed ProcessHeader to return PASS_RECORD when it encountered an empty FCGI_STDIN packet. I'm still analyzing the code to see if there is a cleaner way of doing this using existing logic.

Another update:I got in contact with the maintainer of the FCGI module, and he found a fix for the issue rather quickly. I believe it is being/already committed to FCGI, and the fix (which is in libfcgi) is being sent upstream. Basically, the STDIN stream has to be emptied after each request when using Windows/IIS.

In reply to Has anyone had problems with Perl, IIS, and FastCGI restarting their processes on every POST by Quietly

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.