J. Landman Gay <jacque@...> writes: > So is this something you think I should report? Or is it just a > side-effect of working with different servers? There is a workaround; > specifying a Content-Length header appears to eliminate both the > "Content-Transfer-Encoding" and "Transfer-Encoding: chunked" headers. >
That sounds like a Passenger bug. As Dave said, the 'Content-Transfer-Encoding' header should only be for email. And RFC1341 specifically states "Unlike Content-Types, a proliferation of Content-Transfer- Encoding values is undesirable and unnecessary." I don't know anything about Passenger, but it sounds to me like it's trying to package things up for MIME email transfer. And doing it wrong as well. -- Mark Wieder [email protected] _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
