X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=lib%2FCatalyst%2FResponse.pm;h=186eb0d25b13f976f9063718534dbbe3e2271388;hp=69006e7ee050fe841b274e189577a30b3c1731cd;hb=566678d0245e49d7f2f1abce553b5bdb87879086;hpb=4373973ab65fd23bf7b334a444aba1d526a6f297 diff --git a/lib/Catalyst/Response.pm b/lib/Catalyst/Response.pm index 69006e7..186eb0d 100644 --- a/lib/Catalyst/Response.pm +++ b/lib/Catalyst/Response.pm @@ -205,7 +205,7 @@ handler you are using and might be optimized using server specific abilities (fo example L will attempt to server a real local file in a non blocking manner). If you are using a filehandle as the body response you are responsible for -making sure it comforms to the L specification with regards to content +making sure it conforms to the L specification with regards to content encoding. Unlike with scalar body values or when using the streaming interfaces we currently do not attempt to normalize and encode your filehandle. In general this means you should be sure to be sending bytes not UTF8 decoded multibyte