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

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

How to use HTML template as body to an Email?
by Tushar Dave 28 Jan '16

28 Jan '16

Thanks all for your valuable suggestions. @Rick below is the error that I got when I tried the code that I mentioned in the first post. [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. I might be wrong but that's what I experienced so far. Best, Tushar On Thu, Jan 28, 2016 at 7:00 AM, <dancer-users-request(a)dancer.pm> wrote: > Send dancer-users mailing list submissions to > dancer-users(a)dancer.pm > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > or, via email, send a message with subject or body 'help' to > dancer-users-request(a)dancer.pm > > You can reach the person managing the list at > dancer-users-owner(a)dancer.pm > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of dancer-users digest..." > > > Today's Topics: > > 1. Re: (Rick Leir) > 2. Re: How to use HTML template as body to an Email? (Kadir Beyazl?) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 27 Jan 2016 09:45:56 -0500 > From: Rick Leir <richard.leir(a)canadiana.ca> > To: dancer-users(a)dancer.pm > Subject: Re: [dancer-users] How to use HTML template as body to an > Email? > Message-ID: > < > CAGitpvZpWJx055P8Q-W9pMet9DYztFp83rMK_OCzg04pSouNMA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > There were threads on this recently, I posted config, Perl and tt. There > are a few gotchas but it is quite do-able. What error do you see? > > http://lists.preshweb.co.uk/pipermail/dancer-users/2016-January/005429.html > http://lists.preshweb.co.uk/pipermail/dancer-users/2016-January/005448.html > cheers -- Rick > > > > I am trying to send an email as HTML using HTML template. Does anybody > know > > that how can I use HTML template (that resides in view directory) as > email > > body? So far I tried the following code but am not able to get it > working. > > It may be not the right way of doing it. > > > > try { > > email { > > from => 'abc(a)xyz.com', > > to => 'xyz(a)abc.com', > > subject => 'test email', > > body => template 'contactUsEmail.tt', {name => $params->{'name'}, > > email => $params->email'}, message => $params->{'message'}}, > > type => 'html' > > }; > > >

1 0

How to use HTML template as body to an Email?
by Tushar Dave 27 Jan '16

27 Jan '16

Hello Fellow Dancers, I am trying to send an email as HTML using HTML template. Does anybody know that how can I use HTML template (that resides in view directory) as email body? So far I tried the following code but am not able to get it working. It may be not the right way of doing it. try { email { from => 'abc(a)xyz.com', to => 'xyz(a)abc.com', subject => 'test email', body => template 'contactUsEmail.tt', {name => $params->{'name'}, email => $params->email'}, message => $params->{'message'}}, type => 'html' }; } catch { error "Could not send email: $_"; }; Another possible solution that I am thinking of, I can just store the entire HTML code in a scalar variable and use it as email body (e.g. body => $template, where $tempalte contains the HTML code as $template ="html code.."). Thanks for the help. Best, Tushar Dave

4 3

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

27 Jan '16

There were threads on this recently, I posted config, Perl and tt. There are a few gotchas but it is quite do-able. What error do you see? http://lists.preshweb.co.uk/pipermail/dancer-users/2016-January/005429.html http://lists.preshweb.co.uk/pipermail/dancer-users/2016-January/005448.html cheers -- Rick > I am trying to send an email as HTML using HTML template. Does anybody know > that how can I use HTML template (that resides in view directory) as email > body? So far I tried the following code but am not able to get it working. > It may be not the right way of doing it. > > try { > email { > from => 'abc(a)xyz.com', > to => 'xyz(a)abc.com', > subject => 'test email', > body => template 'contactUsEmail.tt', {name => $params->{'name'}, > email => $params->email'}, message => $params->{'message'}}, > type => 'html' > }; >

1 0

Re: [dancer-users] tt tags
by Rick Leir 23 Jan '16

23 Jan '16

On Tue, Jan 19, 2016 at 7:00 AM, <dancer-users-request(a)dancer.pm> wrote: > [KB] I know that start and end tags of template toolkit can be > defined at config.yml but my problem is that .tt file does not accept > the tags I defined at config.yml. I defined as follow. > > template: "template_toolkit" > engines: > template: > template_toolkit: > start_tag: '<%' > end_tag: '%>' > Sorry for the delay, I was 'otherwise occupied'. And sorry for the changed thread, I receive daily digests so when I rely I have to set the Subject manually. My memory from November is that Dancer2 uses '<%' internally, and I had to use '[%' to avoid conflicts. But I am new to this, please correct

2 1

Dancer2 0.166000 - 404 Behaviour Change
by Dave Cross 23 Jan '16

23 Jan '16

Has something changed (deliberately!) in the handling of 404 errors between Dancer2 0.165000 and 0.166000? I have a project that is being tested with Travis-CI. The last test that used 0.165000[1] worked fine, but (after a few weeks not working on the project) the next test run used 0.166000[2] and failed on two tests[3] that generate 404 errors. I updated my local copy of Dancer2 and found I could reproduce the problem in the web app. The problem seemed to be that the app was always trying to use views/404.tt (which didn't exist) instead of using public/404.html if it can't find views/404.tt - which was the old behaviour. Looking through the Changes file, it seems that it might be related to this: * GH #1093, 1095: Use a dynamic TT2 INCLUDE_PATH to allow relative views with relative includes; fixing regression introduced by #1037. (Russell Jenkins) But I haven't had time to investigate further. I've fixed the problem by adding a views/404.tt file to the project. But I think that's just a workaround. I plan to dig a little deeper into the problem later in the week, but I thought I'd mention it here first in case anyone had any insights that could save me some time. Cheers, Dave... [1] https://travis-ci.org/davorg/lystyng/builds/97884180 [2] https://travis-ci.org/davorg/lystyng/builds/102335005 [3] https://github.com/davorg/lystyng/blob/master/t/004_public_urls.t

3 5

Plack::Test with Cookies
by Dave Cross 23 Jan '16

23 Jan '16

I've been writing tests for a Dancer2 app. I'm using Plack::Test. One thing that I wanted to test was that logged in users get a different view of the app to logged out visitors. For that I need to set cookies on the requests that I'm sending to the test app. I found this advent calendar article by SawyerX which looked very useful. http://advent.perldancer.org/2014/12 Following the instructions in that article, I did this: my $res = $test->request(POST '/login', [ \%test_user_creds ]); $jar->extract_cookies($res); I can look at $jar->as_string before and after that line, and I seen the session cookie being added to the jar. Later I do this: my $req = GET "/$private_page"; $jar->add_cookie_header($req); my $res = $test->request( $req ); This doesn't work. And it doesn't work because the session cookies don't get added to the request object. $jar is a HTTP::Cookies object, so I looked at the add_cookie_header() method, to find this code at the start: my $self = shift; my $request = shift || return; my $url = $request->uri; my $scheme = $url->scheme; unless ($scheme =~ /^https?\z/) { return; } This is where my test goes wrong. My request is just "/$private_page" - it doesn't have a $scheme (or, indeed, a hostname). And I guess it's obvious that add_cookie_header needs a domain in order to know which cookies from the jar to add (my jar only has the correct cookies - but the method can't know that). Looking at the cookie jar, I see that the cookies have been given the domain "localhost.local". Can I just add "http://localhost.local" to the front of my request URL? Is that guaranteed to work in all test environments? Am I missing something here or did that code in the advent calendar article never work? Any advice much appreciated. Cheers, Dave...

3 3

New Dancer2 releases: 0.162000 ... 0.166000!
by Sawyer X 23 Jan '16

23 Jan '16

Hi everyone, I haven't written about our last releases because I was a bit stressed for time. Allow me to apologize for that. We have just released a new version of Dancer2 and I think it's time to share the work we've done recently and where we're going with the next releases. Big changes in 0.166000: * Menno Blom (@b10m) discovered a problem with the interaction of `set` and hooks (GH #1013). This turned up being a race condition which is now fixed. Thanks, Menno! * Alberto Simões (@ambs) discovered a problem with returning 0 as the response content. Working with Russell Jenkins (@veryrusty), they have fixed it. * Andy Beverley (@abeverley) discovered a problem with dynamic include paths in the Template::Toolkit template engine. Russell Jenkins jumped in to help and they fixed the problem! Thanks, Andy, for all the help on researching this! * We somehow ended up being incompatible with 5.8. Our policy is to continue supporting it until we can't. Peter Mottram (@SysPete) worked on sorting this out blazingly fast. We're now compatible again! * Defining routes with DSL now returns the route objects created. This is still experimental but it's available and seems good. Take into account oddities such as `get()` routes returning two objects - one for "GET" and one for "HEAD". If we were to ever serve the HEAD routes through a middleware (which we did and then removed, for speed's sake), this might change. So, experimental and all that. :) It was mainly added to allow us to implement GH #33. Older changes: We have released a few versions who did not receive a proper announcement and I would like to go over the bigger issues: * Bas Bloemsaat fixed a problem in `forward` with a post body re-reading the body filehandle. (GH #1040) * Mickey Nasriachi made sure the `before_serializer` is *always* called, as it should, when a serializer is set. * Thanks to additional work by Mickey Nasriachi, the `before_serializer` hook can now change the content! (via `@_`). * We finally added Hash::MultiValue parameter keywords: `route_parameters`, `query_parameters`, and `body_parameters`. Please use them! We intend to discourage the `param` and `params` keywords. * Dmitrii Tcyganov fixed an error that was triggered when a before hook would set the content. * Dancer2 is a heck of a lot faster now! I want to take a moment to thank the following people for all the work in these versions (in no particular order): Gabor Szabo, Kadir, Vernon, Achilles Kars, Patrick Zimmermann, Andy Beverley, Tina Müller, Dmitrii Tcyganov, A. Sinan Unur, Nick Tonkin, Sébastien Deseille, @girlwithglasses, Nuno Carvalho, Bas Bloemsaat, Mohammad S Anwar, Theo van Hoesel, gertvanoss, Jonathan Scott Duff, and Menno Blom, and thanks to all the core team, especially those involved in this release: Russell Jenkins, Mickey Nasriachi, Alberto Simões, Jason A. Crome, Peter Mottram, and Stefan @racke Hornburg. Future? We finished (!) the new plugin system. Yanick Champoux has moved from focusing on maintaining Dancer 1 to working on Dancer 2. Big thank you to David Precious for taking on Dancer 1 maintenance. Yanick has then worked on rewriting the plugin system. It is now *available* on a branch. We're working tirelessly on making sure plugins continue to work using the old syntax while we start deprecating it in favor of the new system. We intend to throw a lot of warnings (which we will consider reducing) and keep some form of compatibility for a while. In order to reduce the change shock, we're going through as many plugins as possible, trying to smooth them over before having to move to the new plugin system. The ticket to track the current status of it is: https://github.com/PerlDancer/Dancer2/issues/1078 What do you think should be our next major focus? Would you like to help? Let us know! Have a pleasant dancing experience, And thanks for being an awesome community, Sawyer X and the Dancer Core Team. <3

4 6