X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=lib%2FCatalyst%2FUTF8.pod;h=0f20099d18ae26b32e2856e98f79cd17781c80be;hp=eefb181c87062b2452b77d8d451ec2eb9dd4d7d4;hb=80ba671f681862620befead95d299c8dfc91cbaf;hpb=9c056c82094f7550ac9e39408c52d248bcace7b3

diff --git a/lib/Catalyst/UTF8.pod b/lib/Catalyst/UTF8.pod
index eefb181..0f20099 100644
--- a/lib/Catalyst/UTF8.pod
+++ b/lib/Catalyst/UTF8.pod
@@ -462,6 +462,11 @@ B<NOTE> If you try to change the encoding after you start the stream, this will
 response.  However since you've already started streaming this will not show up as an HTTP error
 status code, but rather error information in your body response and an error in your logs.
 
+B<NOTE> If you use ->body AFTER using ->write (for example you may do this to write your HTML
+HEAD information as fast as possible) we expect the contents to body to be encoded as it
+normally would be if you never called ->write.  In general unless you are doing weird custom
+stuff with encoding this is likely to just already do the correct thing.
+
 The second way to stream a response is to get the response writer object and invoke methods
 on that directly: