finished the scheme matching and uri_for updates

[catagits/Catalyst-Runtime.git] / Changes

diff --git a/Changes b/Changes
index 619653c..7c12eb1 100644 (file)
--- a/Changes
+++ b/Changes
@@ -1,6 +1,6 @@
 # This file documents the revision history for Perl extension Catalyst.
 
-5.90080_001 - TBD
+5.90079_001 - TBD
   - MyApp->to_app is now an alias for MyApp->psgi_app in order to better support
     existing Plack conventions.
   - Modify Catayst::Response->from_psgi_response to allow the first argument to
@@ -20,10 +20,19 @@
   - lots of UTF8 changes.  Again we think this is now more correct but please test.
   - Allow $c->res->redirect($url) to accept $url as an object that does ->as_string
     which I think will ease a common case (and common bug) and added documentation.
-  - UTF-8 is now the default encoding (there used to be none...).  You can disable
+  - !!! UTF-8 is now the default encoding (there used to be none...).  You can disable
     this if you need to with MyApp->config(encoding => undef) if it causes you trouble.
   - Calling $c->res->write($data) now encodes $data based on the configured encoding
     (UTF-8 is default).
+  - $c->res->writer_fh now returns Catalyst::Response::Writer which is a decorator
+    over the PSGI writer and provides an additional methd 'write_encoded' that just
+    does the right thing for encoding your responses.  This is probably the method
+    you want to use.
+  - New dispatch matching attribute: Scheme.  This lets you match a route based on
+    the incoming URI scheme (http, https, ws, wss).
+  - If $c->uri_for targets an action or action chain that defines Scheme, use that
+    scheme for the generated URI object instead of just using whatever the incoming
+    request uses.
 
 5.90077 - 2014-11-18
   - We store the PSGI $env in Catalyst::Engine for backcompat reasons.  Changed