Re: [Mojolicious] 'Under' controller method called multiple times

2019-06-19 Thread Justin Hawkins
> On 15 Jun 2019, at 01:02, Dan Book wrote: > > To just "establish a URL path", under is not needed, you can just use any > which does not create a discrete action. Thanks Dan, This worked perfectly. The double call to the previous “under” is still a mystery but no longer a problem.

Re: [Mojolicious] 'Under' controller method called multiple times

2019-06-14 Thread Stefan Adams
On Fri, Jun 14, 2019 at 10:32 AM Dan Book wrote: > To just "establish a URL path", under is not needed, you can just use any > which does not create a discrete action. > Wow, I didn't realize you could use 'any' for this purpose! It makes sense that 'under' must return 1 to continue the chain,

Re: [Mojolicious] 'Under' controller method called multiple times

2019-06-14 Thread Dan Book
To just "establish a URL path", under is not needed, you can just use any which does not create a discrete action. -Dan On Fri, Jun 14, 2019 at 11:32 AM Dan Book wrote: > The explanation is that each 'under' route is a discrete action from the > endpoints, and must be defined and return 1 to

Re: [Mojolicious] 'Under' controller method called multiple times

2019-06-14 Thread Dan Book
The explanation is that each 'under' route is a discrete action from the endpoints, and must be defined and return 1 to continue the dispatch chain. -Dan On Fri, Jun 14, 2019 at 11:10 AM Stefan Adams wrote: > I don't have an explanation for why this seems to be necessary for your > situation,

Re: [Mojolicious] 'Under' controller method called multiple times

2019-06-14 Thread Stefan Adams
I don't have an explanation for why this seems to be necessary for your situation, but after reading Mojolicious::Guides::Routing#Under , I found that this should work for you: # REST interface my $rest_v1 =

[Mojolicious] 'Under' controller method called multiple times

2019-06-13 Thread Justin Hawkins
Hello all, I think there is a good chance this is a case of “holding it wrong”, so I will first explain what I’m trying to achieve. Standard web app, multiple ways of establishing rights to privileged routes. The first is standard username/password, establishing a session. The second is via