- dancer-users - lists.preshweb.co.uk

Dancer::Test response_status_is cleans session data in forward
by Dinis Rebolo 18 Jan '13

18 Jan '13

Hi I was building a test for a app made with dancer and I'm getting a strange behaver... We need to authenticate to access this routes so I store the user in the session. and I have something like this: $route = 'dev'; route_exists [ GET => '/widgets/'.$route ], "a route handler is defined for /widgets/$route"; ## this works fine response_status_is [ GET => '/widgets/'.$route ], 302, 'response status is 302 for /widgets/'.$route; ### this route is a forward to '/widgets'; and after this I loose the session. I was able to trace to where the session is lost and is in Dancer/Test.pm line 378. before this I have user in the session my $get_action = Dancer::Handler::render_request($request); after this I don't have user in the session. Could some one help me here? I'm using the latest Dancer version Thanks -- Dinis Rebolo dinisrebolo(a)gmail.com

1 0

Logging Issues
by James Baer 17 Jan '13

17 Jan '13

Hi All, I'm having some logging issues, that I can't seem to figure out. I have my environment set to development with the following logger settings: logger: "file" log: "core" When I log a "debug" message I'm seeing this error in my main apache error log: (even though I have a virtual host specific error log setup for this app) log directory /var/www/vhost/<appname>/bin/.. isn't writable/executable and can't chmod it at /usr/share/perl5/vendor_perl/Dancer/Logger.pm line 16 According to the docs: "If you're using the file logging engine, a directory appdir/logs will be created and will host one logfile per environment." Why is it saying "bin" isn't writable, when it should be looking for a "logs" directory? Any help would be appreciated Thanks

2 2

Server-Sent Events
by Daniel M. 16 Jan '13

16 Jan '13

Has anyone implemented the following php script in dancer: http://yuilibrary.com/gallery/show/eventsource What I wrote so far is: any ['get', 'post'] => '/chat/:session' => sub { if ( param('view') ){ template 'view', { id => param('session') }, { layout => undef }; }else{ content_type "text/event-stream"; # check every so often to see if there's new data while( 1 ) { # sleep for a second - simulate waiting for data sleep(1); # check for poll-only header if ( my $header = header("X-YUIEventSource-PollOnly") ){ # if it's a poll-only request, break the loop, which ends the request - the client will reconnect last; } return 'data: ' . request->uri_base . request->path . '?view=1'; # Of course it will also end here, the loop does not continue } return 'data: ' . request->uri_base . request->path . '?view=1'; } }; I am still getting some errors in the : src.on("error", function(event){ console.log("Error!"); });

1 0

Coming soon: Dancer::SessionFactory::Cookie
by David Golden 14 Jan '13

14 Jan '13

FWIW, once someone ships a new Dancer 2 dev release with the recent session changes that were merged, I have the next generation of cookie-based sessions ready to go. https://github.com/dagolden/dancer-sessionfactory-cookie It's even more secure than Dancer::Session::Cookie was. David -- David Golden <xdg(a)xdg.me> Take back your inbox! → http://www.bunchmail.com/ Twitter/IRC: @xdg

3 2

Plugin::Auth::Extensible quick patch for logout page
by Rick Bragg 11 Jan '13

11 Jan '13

Hi, May I offer a quick fix for the "any ['get','post'] => $logoutpage => sub" in Plugin::Auth::Extensible? ---- #add a setting for logout redirect page my $logoutredirectpage = $settings->{logout_redirect_page} || '/login'; any ['get','post'] => $logoutpage => sub { session->destroy; redirect params->{return_url} || $logoutredirectpage; }; ---- Just a quick way for when the logout page is hit with a get, it can go somewhere... Thanks! Rick Bragg

1 0

My collected fixes for sessions
by David Golden 05 Jan '13

05 Jan '13

Pull request here for anyone who wishes to review it: https://github.com/PerlDancer/Dancer2/pull/150 David -- David Golden <xdg(a)xdg.me> Take back your inbox! → http://www.bunchmail.com/ Twitter/IRC: @xdg

1 0

How to use SimpleCRUD together with Auth::*?
by chenlin rao 05 Jan '13

05 Jan '13

SimpleCRUD is a good idea. But when I use it to admin my database, I may apply an auth to the routes,how to do this? BTW: I found that SimpleCRUD given an error delete route which omit $args{dancer_prefix}?

3 3

Sessions in D2 (was Before Hook hit multiple times).
by David Golden 04 Jan '13

04 Jan '13

On Thu, Jan 3, 2013 at 11:19 AM, Alexis Sukrieh <sukria(a)sukria.net> wrote: > > I don't get it. Do you have something that works (or is supported) in Dancer > 1 regarding session that is not in Dancer 2? If so, please enlight that, and > I'd be very happy to fix it. Look at the configuration values of Dancer::Session::Abstract. Are all supported in D2? Hint: ack for "session_name" in the D2 source tree, then ack for "dancer\.session". Sessions happened to be the very first thing I was curious about in D2, given bugs I was finding in D1. Then I looked and found a big oversight like session configuration apparently unimplemented. If I find that in the first place I look, should I expect similar oversights elsewhere? Do I need to grok the entire architecture and do a code review to be sure? Maybe I was (un)lucky and found the one place that still has issues, but it's that kind of thing that makes me uncomfortable switching. Did I do a code review of D1? No. But then I expect that a large number of people using it for a few years have found the issues already. (Part of why I came to use Dancer is that it has already been well-established.) On the surface, D2 looks like D1, but it's such a re-write that I don't want to be a super-early-adopter and certainly not until the unimplemented sections I did find are fixed. David -- David Golden <xdg(a)xdg.me> Take back your inbox! → http://www.bunchmail.com/ Twitter/IRC: @xdg

2 6

Proposal: rename Dancer::Session::* to Dancer::SessionFactory::*
by David Golden 04 Jan '13

04 Jan '13

On reflection, I think that it would be wise to rename session factory modules away from "Dancer::Session::*". E.g. Dancer::SessionFactory::YAML instead of Dancer::Session::YAML Sessions work so differently on D2, that existing Dancer::Session plugins are effectively going to be re-written. Managing Dancer::Session::* plugins outside of the core in a way that works with both D1 and D2 is going to be a PITA. If instead, Dancer::Session::* are D1 session plugins and Dancer::SessionFactory::* are D2 session plugins, then things will be quite a bit easier. Existing D1 plugins can stagnate and new D2 plugins can be created. Users migrating from D1 to D2 just need to install the corresponding Dancer::SessionFactory::* (and update their config for the new config structure for sessions), and everything should work fine. David -- David Golden <xdg(a)xdg.me> Take back your inbox! → http://www.bunchmail.com/ Twitter/IRC: @xdg

1 1

Before Hook hit multiple times.
by Rick Bragg 04 Jan '13

04 Jan '13

Hi, I put a simple test in my before hook: hook 'before' => sub { debug "Before Hook"; }; and a couple of quick routes: #Home Page get '/' => sub { template 'index'; }; #About Us page get '/about-us' => sub { template 'about-us'; }; (I am also using Auth::Extensible) Whenever I hit the home page, I get 3 debug messages in a row in the log. Whenever I hit the about-up page, I get 2 debug messages in a row in the log. I thought that any kind of page hook would only be called once. Does anybody know why the before hook would ever be called more than once? Rick

11 27