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

Dancer2::Template::Simple features
by Gabor Szabo 15 Nov '17

15 Nov '17

Hi, reading the source code and then looking at the tests reveal that https://metacpan.org/pod/Dancer2::Template::Simple support both variable interpolation <% var1 %> and conditional statement: <% if var %> true <% else %> false <% end %> The latter however is not documented. Is it because it has not been documented or because this feature is not recommended at all? regards Gabor

1 0

Writing an Auth plugin for SSL client certificates
by perlduck 13 Nov '17

13 Nov '17

Hello, TL;DR I'd like to write an authentication plugin that behaves like Dancer2::Plugin::Auth::Extensible but does NOT require a user's password but instead relies on the SSL variables SSL_CLIENT_VERIFY and SSL_CLIENT_S_DN_Email. Background: I have a Dancer2 application and currently using Dancer2::Plugin::Auth::Extensible to authenticate my users with username/password. I'm currently using two providers (realms), Config and Database. Config is mainly for testing purpose but I like the idea of multiple realms. I also need the concept of roles, so DPAE is just great and everything works like a charm. Now I want to switch to client certificate authentication. I have set up an Apache as a proxy to the plackup server. Apache handles the SSL stuff, sets the variables <Location /> RequestHeader set SSL_CLIENT_VERIFY "%{SSL_CLIENT_VERIFY}s" RequestHeader set SSL_CLIENT_S_DN_Email "%{SSL_CLIENT_S_DN_Email}s" </Location> and then redirects to my Dancer2 app (at 127.0.0.1:5000). Within my routes I can access those variables with my $client_verify = request->env->{'HTTP_SSL_CLIENT_VERIFY'} // ''; my $username = request->env->{'HTTP_SSL_CLIENT_S_DN_EMAIL'} // ''; This works. Apache sets HTTP_SSL_CLIENT_VERIFY to 'SUCCESS' if the authentication worked. What I now want to achieve is: IFF $client_verify eq 'SUCCESS' THEN let the user $username in. Don't show a /login page. Pick the user's details from the database (or whatever realm(s) is/are configured). Don't show a /logout page. In short: allow everything what Dancer2::Plugin::Auth::Extensible allows but without ever asking for a password or redirecting to a /login page if the two variables are set (and, of course, $username can be found in the DB). A very naive first approach was to use a "before" hook to set the "logged_in_user" value: hook before => sub { my $client_verify = request->env->{'HTTP_SSL_CLIENT_VERIFY'} // ''; my $username = request->env->{'HTTP_SSL_CLIENT_S_DN_EMAIL'} // ''; if ($client_verify eq 'SUCCESS' and $username) { session logged_in_user => $username; } }; This seems to work but looks very dirty to me. So I thought I'd better write a plugin that behaves like a Dancer2::Plugin::Auth::Extensible plugin but doesn't require a password and rather uses the two environment variables instead. Is Dancer2::Plugin::Auth::Extensible even the right place (base) for such a plugin? Cheers

3 4

Alexey is inviting you to join italki
by italki.com 24 Oct '17

24 Oct '17

1 0

Question on MongoDB and Dancer
by Gavin Colborne 19 Oct '17

19 Oct '17

Hi Dancers, I am pretty new to Dancer and really like the light nature of the framework. I am trying to create a route which will show data from a MongoDB collection and struggling with the syntax. I have the following in my app: sub connect_mongo { my $client = MongoDB->connect('mongodb://a.b.c.d') or die "Error connecting to Mongo"; my $db = $client->get_database( 'lfi-perl' ); return($db); } get '/mongo' => sub { my $db = connect_mongo(); my $docs = $db->get_collection( 'Test-Collection' ); my $all_docs; template 'show_mongo.tt', { 'entries' => $all_docs = $docs->find(), }; }; Then in my view the following: [% FOREACH id IN entries.keys.nsort %] [% entries.$id._id %] I am not able to see any data in my view but am also not seeing any errors. Any examples of getting data from Mongo in Dancer would be really helpful. Thank you in advance, Gavin Best Regards, Gavin Colborne Managing Director, Tele: 0207 193 2014 Mobile: 0788 400 4339 Skype: gavincolborne Visit: www.littleforest.co.uk [image: Little Forest LFi] <http://www.littleforest.co.uk/>

6 10

Dancer2 0.205002 released; survey update
by Jason A. Crome 17 Oct '17

17 Oct '17

Dancer2 0.205002 has just been released and is on its way to your favorite CPAN mirror. Highlights include a number of documentation improvements (thank you, simbabque and ambs!) and the fixing of some lingering and pesky bugs (thanks to Nick Tonkin, Pierre Vigier, and our very own bigpresh, ambs, and veryrusty). The full changelog is as follows: 0.205002 2017-10-17 16:08:25-05:00 America/Chicago [ BUG FIXES ] * GH #1362: Make cookies http_only by default (David Precious) * GH #1366: Use proper shebang on dancer script and make EU::MM do the job * GH #1373: Unset Dancer environment vars before testing (Alberto Simões) * GH #1380: Consider class of error displayed when using show_errors (Nick Tonkin). * GH #1383: Remove Deflater from default app skeleton (Pierre Vigier) * GH #1385: Fix links inside the documentation (Alberto Simões) * GH #1390: Honour no_server_tokens config in error responses (Russell @veryrusty Jenkins) [ DOCUMENTATION ] * GH #1285: Add "Default Template Variables" section to manual (simbabque) * GH #1312: Fix docs for Dancer2::Core::Route->match, which takes a request object (simbabque). * GH #1368: Don't allow XSS in tutorial (simbabque) * GH #1383: Remove full URL on links to third party modules (Alberto Simoes) * GH #1395: Customize TT behavior via subclassing (simbabque). There's two weeks left in the Dancer 2017 Survey! We have received close to 100 responses now, and are still looking for more. Your input is valuable in charting the future of Dancer. If you have yet to fill out the survey, there's still time. Responses will be accepted until 11:59 PM on October 31st. Until then, keep on Dancing! -- Jason A. Crome / CromeDome CPAN: https://metacpan.org/author/CROMEDOME github: https://github.com/cromedome Twitter: https://twitter.com/cromedome

1 0

advent.perldancer.org seems to be down
by Gabor Szabo 17 Oct '17

17 Oct '17

Hi, http://advent.perldancer.org/ seems it is down both for me and for another one: http://downforeveryoneorjustme.com/advent.perldancer.org Gabor

3 3

D1 throwing strings, not always Dancer::Exceptions
by Warren Young 17 Oct '17

17 Oct '17

I just needed to hook on_handler_exception in a D1 app for the first time, and was surprised to find that it doesn’t obey [the docs][1]: hook on_handler_exception => sub { # The docs say we're passed a Dancer::Exception object, but that is # not true: we are sometimes passed a plain string! my $exception = shift; my $msg = ref($exception) ? $exception->message() : "STR[$exception]"; ... Simple test case: drop this into a route while Perl strict mode is enabled: debug 'This will throw an error ' . undef; You will get the STR[message] form above. [1]: https://metacpan.org/pod/Dancer#hook

1 0

Problems writing a Plugin
by Alfonso Pinto 13 Oct '17

13 Oct '17

Dear all, I'm trying to write a Dancer2::Plugin to maintain ZMQ socket and send some information to a backend when a request is received. This is the plugin : > package Dancer2::Plugin::ZMQ; > > > use Dancer2::Plugin; > > > use ZMQ::FFI; > > use ZMQ::FFI::Constants qw(ZMQ_REQ); > > > has host => (is => 'ro'); > > has identity => (is => 'ro'); > > > has _context => (is => 'ro', lazy_build => 1); > > sub _build_context { > > my $plugin = shift; > > return ZMQ::FFI->new(); > > } > > > has client => (is => 'ro', lazy_build => 1, plugin_keyword => 'zmq'); > > sub _build_client { > > my $plugin = shift; > > > my $client = $plugin->_context->socket(ZMQ_REQ); > > $client->set_identity = $plugin->config->{identity} . "-$$"; > > $client->connect($plugin->config->{host}); > > return $client; > > } > > > 1; > This is my config.yml: plugins: > ZMQ: > identity: "api-gw" > host: "tcp://proxy:6660" And this is how I use it in one route: post '/' => sub { my $message = body_parameters->get('message'); zmq->send(message =>$message); my $reply = zmq->recv(); return {"reply" => $reply}; }; The issue is that I get this error: > Router exception: Can't call method "send" on an undefined I don't understand why it's not keeping the client instantiated. What is wrong withmy approach? What I don't want is to create a socket for each request received. And before someone asks, the backend is working and replying. A simple script like this one works in my setup: use v5.10; > use ZMQ::FFI qw(ZMQ_REQ); > my $endpoint = "tcp://proxy:6660"; > my $ctx = ZMQ::FFI->new(); > my $s1 = $ctx->socket(ZMQ_REQ); > $s1->connect($endpoint); > $s1->send('ohhai'); > print $s1->recv(); Thanks in advance. Regards, Alfonso

2 5

Apache config settings that should work for www.perldancer.org rerwite
by Dave Baker 09 Oct '17

09 Oct '17

# Send www.perldancer.org requests to perldancer.org # # From httpd.apache.org/docs/2.2/mod/mod_rewrite.html: # "In VirtualHost context, The Pattern will initially be # matched against the part of the URL after the hostname and # port, and before the query string (e.g. "/app1/index.html")." # RewriteCond %{HTTP_HOST} ^www\.perldancer.org [NC] RewriteRule ^(.*) https://perldancer.org$1 [R=301] On 10/6/2017 7:00 AM, dancer-users-request(a)dancer.pm wrote: > > Hello Gabor, > > thanks for spotting this. I agree with you, we should permanently redirect > from www.perldancer.org to perldancer.org. > > Regards > Racke > -- Dave Baker

1 0

Dancer examples
by Gabor Szabo 08 Oct '17

08 Oct '17

Hi, is there a place with a bunch of working examples? If not, I wonder if adding a bunch of them to the Dancer2 repository, together with tests checking them would be a good idea? Here is the issue I opened with an example example: https://github.com/PerlDancer/Dancer2/issues/1386 reagrds Gabor Check out my Dancer SPA book: https://leanpub.com/dancer-spa/

1 0