Thanks for all your pointers. I'll see what makes most sense when I get my
hands dirty.
For many reasons, it probably is a good idea to refactor our shared
utilities to take query parameters as arguments somehow instead of
extracting them from $c or global context anyway, so thats my plan for
Ok, thanks! It helps to understand the reasons behind why things are as as
they are.
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I'm just getting my feet wet with Mojolicious. One of the things I loved
immediately was Mojo::Template, so I've started using it also outside of
Mojolicious. I was very surprised to see error output on STDOUT without my
$SIG{__DIE__} kicking in.
So now I am curious as to why it returns
I'm having trouble with all the different ways of setting
inactivity_timeout.
http://mojolicious.org/perldoc/Mojolicious/Guides/FAQ#What-does-Inactivity-timeout-mean
says:
> It defaults to 20 seconds for the user agent and 15 seconds for all
> built-in web servers, and can be changed with the
r now. :-)
Peter
On Mon, Nov 7, 2016 at 12:35 PM, Peter Valdemar Mørch <pmo...@gmail.com>
wrote:
> Hi,
>
> Today we encountered an exception in a source file that wasn't in UTF-8.
> This caused first a warning and then an error in the morbo output. Apache2
> showed a "50
Hi,
Today we encountered an exception in a source file that wasn't in UTF-8.
This caused first a warning and then an error in the morbo output. Apache2
showed a "502 Proxy Error: Error reading from remote server" from in our
apache2+morbo setup.
The file on-disk is "binary", because it uses a
Say in my controller I'm 5 levels deep and discover there is a problem with
the user's input. I call:
$c->render(
template => 'errors/badValues',
message => 'The value of foo cannot be "bar"',
);
And now I want to stop the entire request right there. I guess the
behaviour