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

set vs var
by Hermann Calabria 23 Feb '16

23 Feb '16

I’m using D1, and have a before hook that sets a var with a payload of session/client-specific values. This works well when running D1 normally as a web app. However there are a few tasks that need to run via a daily cron job, for which I load D1 manually. In those cases I lose the vars setting, even if I set them manually, knowing the hook does not execute. The following snippet: use strict; use Dancer ':syntax'; Dancer::Config::setting('appdir', '/home/s1/www/'); Dancer::Config::setting('views', '/home/s1/www/views'); config->{'environment'} = 'development'; Dancer::Config::load(); var hello => "hi, I used var"; set hello => "hi, I used set"; print template('test', {}); # uses Template Toolkit with the following template test.tt: Hello using vars = <% vars.hello %> Hello using settings = <% settings.hello %> yields: Hello using vars = Hello using settings = hi, I used set In this case, ‘vars’ is not passed on to Template Tookit, whereas ‘settings’ is. If I had run this within a normal D1 route, ‘vars’ would have been passed. So it appears I need to refactor the entire (large) application to use “set” and not “var”. Is this correct? Why isn’t “var” the correct option here? Or if it is, what am I doing wrong? Thx in advance! Hermann

2 2

Dancer1 dev release 1.3300 released - new stable release expected soon
by David Precious 16 Feb '16

16 Feb '16

Hi all, I've just pushed a new dev release of Dancer 1 to CPAN, version 1.3300. It contains an assortment of bug fixes and minor improvements - changelog below for convenience. If you use Dancer1, please consider testing your code using this version, and do let me know if it breaks anything for you. Assuming nobody screams and the CPAN Testers results look good, I plan to push out a new stable release later this week. [BUG FIXES] - More temp directory handling fixes (Issue #1147) - Avoid request body truncation in hand-assembled requests in tests (PR 1148, skington) - Avoid tests failing when "localhost" doesn't resolve (PR 1142, gbarco) - Avoid test failures due to race condition in selecting a port to listen on by using 127.0.0.10 instead (more of a hacky workaround than a fix, but should help (bigpresh) - Fix YAML session handler under taint mode (chrisjrob) - Make request->body work again for URL-encoded POST requests - Issue 1140 reported by miyagawa (bigpresh) - Validate session IDs read from cookies before passing to session engine, to protect against any engine that might feed that value straight to a file path for security - Issue 1118 (bigpresh) [DOCUMENTATION] - Better doc for forward_for_address (PR 1146, Relequestual) [ENHANCEMENTS] - Let Dancer::Test::dancer_response() handle supplying multiple params with the same name - Issue 1116 (bigpresh) Cheers, Dave P (BIGPRESH)

2 2

New session on reload using Apache CGI
by mark jones 15 Feb '16

15 Feb '16

Hi, I was just doing some testing deploying a Dancer2 app under Apache using CGI. For some reason I get a new session each time the page reloads, does anyone know why? It works fine with plackup. I am using AMPPS so it could just be something screwy with my config. Dancer App2 snippet get ‘/' => sub { session Name => ‘foo’; Dumper(session); }; get ‘/name' => sub { return session('Name'); }; Apache conf <VirtualHost *:80> ServerName localhost DocumentRoot "/testing" RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f <Directory “/testing"> AllowOverride None Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch Order allow,deny Allow from all AddHandler cgi-script .cgi </Directory> RewriteRule /App2(.*)$ /App2/public/dispatch.cgi$1 [QSA,L] </VirtualHost> Cheers Mark

3 5

Basic authentication and Dancer
by WK 12 Feb '16

12 Feb '16

Hi! I try to run one simple Dancer app behind Apache proxy and because there is a bunch of old CGI scripts running on same server, restricted by basic authentication, I'd like to use the same authentication scheme in Dancer app too. My Apache config looks like this: <Location /xyz/z > ProxyPass http://localhost:5001 ProxyPassReverse http://localhost:5001 RequestHeader set Request-Base /xyz/z AuthName "myadmin" AuthType basic AuthUserFile /etc/htpasswd.adm Require valid-user </Location> So far, so good. Problem: in Dancer I can't access env variable REMOTE_USER. AFAIU Dancer::Request object does not forward this variable. What is the best way to access REMOTE_USER value inside Dancer? Tia, -- Wbr, Kõike hääd, Gunnar

4 9

Dancer::Plugin::Email taint
by Mike Cu 11 Feb '16

11 Feb '16

When using the Dancer::Plugin::Email module,should you check the user input for tainted data? like for the classic rm -rf?

2 1

Re: [dancer-users] How to use HTML template as body to an Email?
by Rick Leir 01 Feb '16

01 Feb '16

I have not been using multipart so far, though I may do in the future. HTH. use Email::MIME::CreateHTML; use Email::Sender::Simple qw(sendmail); use Email::Sender::Transport::SMTP qw(); ... my $email_body = template( $tt, \%fields, ); # produce an Email::Abstract compatible message object, my $email = Email::MIME->create_html( header => [ From => $fields{email_from}, To => $fields{email}, Subject => $fields{email_subject}, ], body => $email_body, ); try { sendmail($email, { from => $fields{email_from}, transport => Email::Sender::Transport::SMTP->new({ host => config->{smtp_server}, port => config->{smtp_port}, }), } ); } catch { .. [testemail:37988] error @2016-01-26 14:46:09> Route exception: Could not > send email can't build entity: no body, and not multipart > > I am getting a multipart warning because I didn't specify "multipart => > 'related'" in email function. I believe, Dancer2 requires "multipart" to > be set to "related" when you want to send HTML emails.

1 0