fpCGI failure, part 2

[Fairlight]

Four score and seven years--eh, screw that!
At about Wed, Mar 19, 2008 at 09:16:02AM -0700,
Tyler blabbed on about:
> Just in case anyone's still interested in my fpcgi saga, here's an update.
> 
> Adding an entry to the submitted forms for the nohtmlreturn field didn't
> resolve the issue.  There were minor bomb outs (meaning the filepro
> processing didn't run and no output was produced) throughout testing, but
> after about 5 days it stopped outputting anything for any report.
> 
> Working with fptech on the issue, so may have more to follow up with after
> speaking with them.

By the time you've reached this point, you could have migrated to OneGate
and been done with all these problems, more than likely.  And had better
security and more features.  And a lower Tylenol bill.

You mentioned doing AJAX work with fpcgi.  How are you getting around the
inability of fpcgi to change MIME types on errors?  Browsers are -really-
picky about the type for the response to the XMLHTTPRequest object.  Or is
it just really ugly when it errors?  :)

mark->
-- 
"Moral cowardice will surely be written as the cause on the death
certificate of what used to be Western Civilization." --James P. Hogan