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

Plugin::Database failed on reconnect
by WK 12 Apr '12

12 Apr '12

Hi! My little application stand whole night and when on morning user made first request, app did not connect properly to Database. Error was like: DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '&amp;amp;amp;amp;amp;amp;amp;amp;#39;utf8&amp;amp;amp;amp;amp;amp;amp;am' at line 1 at /usr/local/share/perl/5.12.4/Dancer/Plugin/Database.pm line 198. /usr/local/share/perl/5.12.4/Dancer/Plugin/Database.pm around line 198 195 return; 196 } elsif (exists $settings->{on_connect_do}) { 197 for (@{ $settings->{on_connect_do} }) { 198 $dbh->do($_) or Dancer::Logger::error( 199 "Failed to perform on-connect command $_" 200 ); 201 } As i use also Plugin::EscapeHTML with automatic_escaping: 1, it seems that there is some problem with 2 of them together. At least there is made some weird escaping. Or? After restarting app, connenction to DB was alright. Main problem: how to avoid reconnecting failure? -- Wbr, Kõike hääd, Gunnar

3 5

UTC timestamp for logger_format
by Alex C 12 Apr '12

12 Apr '12

I noticed that Dancer gets its timestamps using localtime(). I prefer to have all my logs in UTC. Please can I suggest the following patch to Dancer::Logger::Abstract to provide an option for this? @@ -94,6 +94,7 @@ sub format_message { t => sub { Encode::decode(setting('charset') || 'utf8', POSIX::strftime( "%d/%b/%Y %H:%M:%S", localtime )) }, T => sub { POSIX::strftime( "%Y-%m-%d %H:%M:%S", localtime ) }, + U => sub { POSIX::strftime( "%Y-%m-%d %H:%M:%S", gmtime ) }, P => sub { $$ }, L => sub { $level }, D => sub { -- Alex

4 4

Config Setting "behind_proxy: true" gives incorrect proxied protocol
by Gurunandan Bhat 05 Apr '12

05 Apr '12

Hi, I am hosting a Dancer Web Application behind an Apache proxy using the recommended (in Dance::Deployment) configuration. The application can be accessed via a secure URL: https://some.domain.comand I have set 'behind_proxy: "true"' in my config.yml. However when I use [% request.uri_base %], I get http://some.domain.com and not https://some.domain.com which is what I am expecting. Is there a way to have request.uri_base return the correct proxied protocol (in this case https) rather than 'http'? Thank you - Gurunandan

3 5