Re: dieGif? It's been broken for some time it seems.
Reply #17 –
That fixes it. No errors in the log and the response has gif headers.
Re: dieGif? It's been broken for some time it seems.
Reply #18 –
So really since you know it's going to end in dieGif don't you want to send the gif right before you call fast_cgi_finish? Then go process the scheduled tasks and simply return w/o any further data where you previously called dieGif?
Re: dieGif? It's been broken for some time it seems.
Reply #20 –
Effectively anyone running fastcgi has been sending an empty page. I never notice anything browser wise to tip me off that it was sending an empty page in an img tag. I agree the send a gif seems an odd choice over an empty page.
Re: dieGif? It's been broken for some time it seems.
Reply #21 –
I think the 1px gif is an heritage of the old days when browsers may complain about an empty responses.
Okay, let's take a look at dropping this stuff once and for all! xD