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

Debugging sessions
by Nikola Mitev 29 Jun '23

29 Jun '23

Hi all, I have an annoyingly intermittent problem where on successful authentication the session info disappears and the user is endlessly redirected to the login page. It happens about once a month on a site with 10-20 logins daily. Once it happens to a user, it keeps happening for that user only. A restart of the app usually fixes the issue, and I am yet to see someone who had this problem to report it again at a later stage. Had about 10 cases so far in total. The cookie is generated on accessing the login page, stored in the browser and sent with the login POST request so I can verify cookies are enabled. The user is then authenticated, data added to the session including an 'authenticated' flag and they are redirected to their dashboard. Right before the redirection the session data is present. They make a request for the dashboard following the redirect, this triggers a session authenticated check which fails as no data is available for the session. They are then redirected for authentication and so on in a loop. If I restart the app the issue vanishes. hook before => sub { # <snip> if (!session('authenticated')) { forward '/login'; } } post '/login' => sub { # user authentication and session storage here, then the debug code and the redirecton: my $authenticated = session('authenticated'); $log->info("User authenticated ($authenticated), redirecting to $target_route"); return redirect $target_route; }; I don't have an explicit check on cookie size - not sure how to check it doesn't exceed 4K - but find it unlikely this is the issue. If that was the problem it should be happening persistently for a user regardless of restarts etc? Hope all this makes sense, I am looking for general advice on how to troubleshoot this but any ideas at all will be very much appreciated. Nik

4 11

status issue
by Lyn St George 27 Feb '20

27 Feb '20

Trying to send a 'status 200' back to Stripe from a webhook, using D2 0.30000, perl 5.30.0 on Gentoo. Using either: status 200 Dancer2::Core::HTTP->status(200); $self->app->response->status( '200' ); or indeed nothing (as D2 apparently sends a status anyway), the result is: Route exception: Undef did not pass type constraint "Num" (in $self->{"status"}) at /usr/local/lib64/perl5/5.30.0/Dancer2/Core/DSL.pm line 279 "Num" is a subtype of "LaxNum" "LaxNum" is a subtype of "Str" "Str" is a subtype of "Value" "Value" is a subtype of "Defined" Undef did not pass type constraint "Defined" (in $self->{"status"}) "Defined" is defined as: (defined($_)) in /usr/local/lib64/perl5/5.30.0/Dancer2/Core/App.pm l. 1488 Cheers Lyn

2 3

Re: [dancer-users] Capturing an exception thrown in the routes? on_route_exception
by Luis Ernesto Gonzalez Cardenas 24 Feb '20

24 Feb '20

Hello Gabor, Did you receive any response about this question? I’m fighting with the same issue, how should I use the on_route_exception? Regards, Luis Cardenas.

1 0

Social Login with Dancer2
by Dave Cross 12 Feb '20

12 Feb '20

Hi all, For a project I'm about to start on, I want to add social login (Google/Twitter/Facebook) to an existing Dancer2 app. I could dive in and teach myself how it all works, but I thought it might save a bit of time if I could see how someone else has done it and borrow a line or two of code. So if anyone has an example that I could look at, that would be great. Cheers, Dave...

3 2