[Catalyst] C::P::Unicode::Encoding and C::P::Compress

[Nicholas Wehr]

are you using the built-in perl http server for your production deployment?
if not, consider apache's mod_deflate for your gzip content.

I ran into a similar issue with dynamic tar file output; using a temp file
barfed (from utf8) - streamed was fine.

good luck
-nw


On Wed, Jul 28, 2010 at 10:25 PM, Octavian Rasnita <orasnita at gmail.com>wrot=
e:

> Hi,
>
> I have been using Catalyst::Plugin::Unicode but I read in its POD that
> Catalyst::Plugin::Unicode::Encoding is now recommended.
>
> Can C::P::Unicode::Encoding be used with C::P::Compress::Gzip or
> C::P::Compress?
>
> I've seen that the HTTP headers seem to be correctly generated, but no pa=
ge
> content is sent if I use these 2 plugins.
>
> I have used the following settings in the configuration file:
>
> encoding UTF-8
> compression_format gzip
>
> Thanks.
>
> Octavian
>
>
> _______________________________________________
> List: Catalyst at lists.scsys.co.uk
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive:
> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
> Dev site: http://dev.catalyst.perl.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20100728/c01eb=
779/attachment.htm