[dancer-users] Delayed template processing

[Joerg Fallmann]

Hi,
You are of course absolutely right,
my idea of a workaround was to implement sessions into my app.
I now store some variables from one route in cookies
to be able to retrieve those variables from other routes.
So far this seems to work fine and should solve the problem
--joerg

On 10/16/2015 06:34 PM, WK wrote:
> 2015-10-16 16:11 GMT+03:00 Joerg Fallmann <fall at tbi.univie.ac.at>:
>
>> Thanks to everyone involved I finally managed to get it done;
>>
>> For people with the same problem, here is an example for what I did,
>>
>> my $parameterhash;
>> get '/routeA/:*?' => sub {
> Maybe you are thought on that, but to be clear, your example is
> basically equal to following:
>
> my $parameterhash;
>
> get '/routeA' => sub {
>     my $id = params->{'id'};
>     my $blub = params->{'blub'};
>
>     $parameterhash = {
>             'id' => $id,
>             'bla' => $blub
>         };
>
>     return "routeA: $id $blub";
> };
>
> get '/routeB' => sub {
>     my $id = $parameterhash->{'id'};
>     my $blub = $parameterhash->{'bla'};
>
>     return "routeB: $id $blub";
> };
>
> Without some serious counter measures this pattern has huge security
> problem. If any user points routeA, then any other request to routeB
> has same data available.
>
> Wbr,