view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

0.13  Thu Jun  9 23:58:10 PDT 2011
        - Fixed a bug in PSGI header generation to prevent potential HTTP header injection
        - Misc doc fixes

0.12  Thu Jan  6 14:37:53 PST 2011
        - Fix for Catalyst::Runtime >= 5.80030 (pedromelo)

0.11  Fri Jul 30 12:49:46 PDT 2010
        - Allows setting a code reference to the $c->res->body as
          a raw PSGI streaming (t0m)

0.10  Thu May 20 14:38:03 PDT 2010
        - Added docs for frontend proxy and X-Forwarded-* headers

0.09  Wed Apr  7 20:17:57 PDT 2010
        - Escape :: in the helpers for .psgi files (lestrrat)

0.08  Fri Mar 19 00:58:35 PDT 2010
        - Fixed a problem with URLMap where root access gets an empty path (omega)

README  view on Meta::CPAN

    Catalyst::Engine::PSGI is a Catalyst Engine that adapts Catalyst into
    the PSGI gateway protocol.

COMPATIBILITY

      * Currently this engine works with Catalyst 5.8 (Catamoose) or newer.

      * Your application is supposed to work with any PSGI servers without
      any code modifications, but if your application uses $c->res->write
      to do streaming write, this engine will buffer the ouput until your
      app finishes.

      To do real streaming with this engine, you should implement an
      IO::Handle-like object that responds to getline method that returns
      chunk or undef when done, and set that object to $c->res->body.

      Alternatively, it is possible to set the body to a code reference,
      which will be used to stream content as documented in the PSGI spec.

      * When your application runs behind the frontend proxy like nginx or
      lighttpd, this Catalyst engine doesn't automatically recognize the
      incoming headers like X-Forwarded-For, because respecting these
      headers by default causes a potential security issue.

lib/Catalyst/Engine/PSGI.pm  view on Meta::CPAN

=over 4

=item *

Currently this engine works with Catalyst 5.8 (Catamoose) or newer.

=item *

Your application is supposed to work with any PSGI servers without any
code modifications, but if your application uses C<< $c->res->write >>
to do streaming write, this engine will buffer the ouput until your
app finishes.

To do real streaming with this engine, you should implement an
IO::Handle-like object that responds to C<getline> method that returns
chunk or undef when done, and set that object to C<< $c->res->body >>.

Alternatively, it is possible to set the body to a code reference,
which will be used to stream content as documented in the
L<PSGI spec|PSGI/Delayed_Reponse_and_Streaming_Body>.

=item *

When your application runs behind the frontend proxy like nginx or