On 5/21/2015 2:37 PM, Mark Wieder wrote:
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.
Thanks. I'm inclined to agree with you because Passenger 3.x didn't do
that. The problem showed up in version 5 after we updated the server.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
