On 27 Nov 2012, at 20:11, Jaroslav Zajonc wrote:
Hi all,
I'd like to enable my Catalyst based (FastCGI) application to support a Comet
(Long polling) service with help of Twiggy - Pocket.IO (or Stardust like)
server. Now, for my Comet server I still want to use Catalyst app for
But if I direct traffic from Apache directly to Twiggy server
I'd bypass Catalyst Authentication/Authorization part for Comet session,
right?
I'd like to allow only authenticated users to subscribe to comet channel.
I am sure I am missing some really simple piece of the puzzle :-\
br,
Jaro
On 28
On Nov 28, 2012, at 9:21 AM, Jaro Zajonc jaro.zaj...@gmail.com wrote:
But if I direct traffic from Apache directly to Twiggy server I'd bypass
Catalyst Authentication/Authorization part for Comet session, right?
I'd like to allow only authenticated users to subscribe to comet channel.
I am
I also faced this problem, and what I did to resolve it was move the
authentication piece out to Apache (from my Catalyst application), and then
used the Catalyst::Authentication::Credential::Remote module to 'use' what
Apache is doing for me. Once the auth config is in Apache, you can use it
to
Hi all,
Thanks a lot for all your suggestions. Yu helped me a lot.
thnx,
Jaro
On Nov 28, 2012, at 4:38 PM, Tim Anderson tja...@gmail.com wrote:
I also faced this problem, and what I did to resolve it was move the
authentication piece out to Apache (from my Catalyst application), and then
I use a log4perl config file, and I have two appenders -- one is for INFO
and above and is a screen appender (web server logs), and the other is for
ERROR and is directed to a separate file.
For *only *WARN and above messages I want to include a dump of request
parameters in the log message.
On Wed, Nov 28, 2012 at 4:21 AM, Jaro Zajonc jaro.zaj...@gmail.com wrote:
But if I direct traffic from Apache directly to Twiggy server
I'd bypass Catalyst Authentication/Authorization part for Comet session,
right?
I'd like to allow only authenticated users to subscribe to comet channel.
I