I ran into a bug migrating a mod_cgi script from Apache 1.3 to Apache 2.0. Doing some research, I found a lot of various people having this problem (one
here). Suspecting the new filtering system, I came up with a
fix ( A mod_perl output filter) that solved it for me. I suspect that it would help out in the other instances I ran across.
Configuring and installing a mod_perl handler seems like a lot of work to avoid this problem. Is there an easier way to do it that anyone can think of? I don't have a problem changing my configs and what not as I usually have total access and control of any boxes I work on, so I'm all set. But I realize others might not. Many probably don't have access to mod_perl at all. I'd like to come up with something that works for everybody so maybe I can help someone else avoid all the head pounding trying to figuring out what's wrong. I certainly would have appreciated finding a solution when I first ran into it.
I suppose I could try and modify the mod_cgi source and have some sort of flag or something, but getting into the bowels of Apache and submitting patches is beyond my means (and motivation) right now. Hoping someone has a clever perl side idea.
Any thoughts?
-Lee
"To be civilized is to deny one's nature."