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

DPAE logging
by Nathan Bailey 13 Jun '17

13 Jun '17

Hi all, I'm trying to work out why my permission_denied_page_handler isn't working in Dancer2::Plugin::Auth::Extensible. However, as a separate problem I get none of DPAE's logging messages. If I write: app->log(core => "Testing 1..2..3.."); in my app, this message doesn't appear anywhere in my log files. Where should it be going/appearing? Note that this is true whether I use 'logger: File' or 'logger: LogReport' thanks, Nathan PS: Pertinent to the original problem, if I dump app, I can see that permission_denied_page_handler *has* been set to MyApp::permission_denied_page_handler but the subroutine in MyApp.pm never gets called.

2 2

Command line change password script (Was: Custom login page with Dancer2::Plugin::Auth::Extensible)
by Nathan Bailey 26 May '17

26 May '17

Hi all, Separate but somewhat related to my previous questions - how can I make a command line script to do a change password, using the DPAE infrastructure? Presumably I will need to use Dancer2? Or can I dig directly into DPAE's set_user_password()? Dancer2::Plugin::Auth::Extensible::Provider::Database->new() wants a 'plugin', and Dancer2::Plugin::Auth::Extensible->new() wants an 'app'; I could pass fake values in but I suspect that's going to break things. How far up the tree do I need to go to be able to say "Use XXX", "XXX->new" and "XXX...->set_user_password"? thanks, Nathan

2 2

DPAE workflow: password reset => change password, rather than temporary password?
by Nathan Bailey 26 May '17

26 May '17

Hi all, I now have Dancer2::Plugin::Auth::Extensible working in our environment. It works great, but I think the 'forgot password' workflow is a little longer than it needs to be. It appears that the 'Forgot password' workflow is: 1. Type in email and request token 2. Get token in email 3. Click the link with the token (in your email) 4. Click 'Reset password' 5. Get a new password 6. Login in with the new password 7. Presumably, change your password It seems that steps 5 and 6 are redundant to me - once we've authenticated the user, I'd like to get them to change their password immediately. Presumably others have already done this, does anyone have some code they'd like to share? thanks! Nathan

1 0

Printing output directly
by Amelia Ireland 23 May '17

23 May '17

Hello Dancers, Is it possible to print web page output directly using Dancer2? I'm using Text::CSV_XS to output DB data as CSV like so: while ( my $row = $sth->fetch ) { $csv->print ( $io, $row ); } where $io is a file handle, socket, etc. At the moment, I'm creating a temp file, writing the data, and then using send_file to dispatch the data. Ideally I'd like to just print it straight to the web output, but (e.g.) setting $io to *STDOUT does not work, and there is no serialiser for csv or plain text. Is there a shortcut that I'm missing? Thanks!

2 1

query parameter parsing and Dancer vs Apache handling
by Amelia Ireland 15 May '17

15 May '17

Hi Dancers, Is it possible to have Dancer selectively handle some routes based on query parameters, and leave others for another script to handle? I'm working with an old site where some URLs with query params of the form main.cgi?param=value&param2=value2&param3=value3 can be handled by Dancer (by redirecting to new pages), but others must be handled by the old site. At present, I have a route set up to parse query params for /main.cgi, and any query params that Dancer can't handle go to the 404 page. Is there are way to let those queries 'pass through' dancer (i.e. not trigger a 404) and be handled by the perl script main.cgi instead? If I set up Apache or my psgi application to send all those queries to main.cgi first, the subset of pages that can be redirected by new pages will just show the old page. Unfortunately I cannot change the content of the old pages to change the URLs. I'd guess I can create Apache redirects for sets of query parameters -- it's pretty easy to specify that only certain combinations of query params are handled by Dancer, and I'm not sure it is as easy a task with Apache. Thanks!

2 1

Custom login page with Dancer2::Plugin::Auth::Extensible
by Nathan Bailey 15 May '17

15 May '17

Per the documentation, http://search.cpan.org/~hornburg/Dancer2-Plugin-Auth-Extensible-0.703/lib/D… in my .yml config, I have: plugins: Auth::Extensible: # Set the view name for a custom login page, defaults to 'login' login_template: login but my login page: get '/login' => sub { ... template 'login', { ... }; }; doesn't seem to get called. I've tried "login_template: /login" but the default login is still getting loaded. Any ideas? thanks! Nathan

3 5

Re: [dancer-users] (no subject)
by Stanley Lankford 12 May '17

12 May '17

Hi , Get your low interest loans today. with interest rate as low as 8% per annum we're hard to beat bad credit score? no problem! we have a solution for everyone. just send us an email to: stanley.lankford(a)gmail.com for more information.

1 0

TT 'include file if exists'
by Nathan Bailey 01 May '17

01 May '17

Hi all, More of a Template Toolkit question rather than Dancer per se, but is there a better way to load a file only if it exists? >From my Googling around, it appears the only approaches are (a) Try/Catch in TT or (b) include a full <%PERL%> call (which I'm guessing may be a little heavy to do on every page load). I'd like to dynamically include a help file if it exists, otherwise provide a 'No help available for this page' message. Current code looks like this: <% help_file = 'help' _ request.request_uri.remove('\?.*') _ '.tt' %> <% TRY %> <% USE File('/full_unix_path/views/' _ help_file) %> <% INCLUDE $help_file %> <% CATCH File %> '<% help_file %>' doesn't exist: <% error.info %> <% END %> I'm not keen on the fixed path and it seems overkill to have to try/catch if the file exists rather than just load it (and fail silently) or test if it exists and then load. Do people have better patterns for managing inline help? thanks, Nathan

3 2

Second cookie [ for 'remember me' username only ]
by Nathan Bailey 24 Apr '17

24 Apr '17

Hi all, I'd like to have a 'remember me' cookie for users who want their username to be remembered by the browser (but not the password). Dancer2::Core::Role::SessionFactory's set_cookie_header seems quite specific to sessions, so it appears that the right/best way to do it is to use push_header (as set_cookie_header does), viz: if (is_successful_login && defined params->{remember_me} && params->{remember_me}) { push_header( 'Set-Cookie', (remember_me_user => session('user')) ); } Is there a well-defined pattern for this? cheers, Nathan

2 2

Starman large file upload
by Zahir Lalani 18 Apr '17

18 Apr '17

Hi All Hit a bit of a wall We are using a standard jquery uploader connected to Dancer2 and that in general works great We are testing uploading large files (600M) and having a lot of issues: We see the file uploading to /tmp as expected. At the end of the upload, Starman has a lot of CPU and Mem usage and the defined upload route (our code) does not get hit for several minutes. It looks like Starman is loading this into memory and hitting swap issues Apart from increasing memory - is there something specific we should be doing to resolve this? Zahir Lalani Head of Development & Architecture [cid:96F784CA-E917-4CC1-A9A9-96CBDA2AF2BC] 151 Rosebery Avenue, London, EC1R 4AB m: +44 (0)7956 455168 t: +44 (0)203 142 3619 e: zahirlalani@oliver<mailto:zahirlalani@oliver-marketing.com>.agency w: www.oliver.agency

3 3