Nevermind, I think I got it sussed.
My controller was locked down so only logged in admins could trigger the
task, and so was the end point. Obviously the Task Queue could not be
logged in, so it failed.
I'm guessing the best way to secure a task end point is to set a handler
and use login:
login: admin is the way we do them as well.
On Friday, November 13, 2015 at 5:00:25 AM UTC-5, Paul Canning wrote:
>
> Nevermind, I think I got it sussed.
>
> My controller was locked down so only logged in admins could trigger the
> task, and so was the end point. Obviously the Task Queue could
Yea, I may also implement checking the request headers that the push tasks
queue sets.
Cheers!
On Friday, November 13, 2015 at 1:45:01 PM UTC, Joshua Johnston wrote:
>
> login: admin is the way we do them as well.
>
> On Friday, November 13, 2015 at 5:00:25 AM UTC-5, Paul Canning wrote:
>>
>>
Can you show us what the handlers section of your yaml looks like for the
non-working module?
On Thursday, November 12, 2015 at 12:42:42 PM UTC-5, Paul Canning wrote:
>
> I have a CI app and I am trying to get Push Tasks to work.
>
> I have a controller, controller_a, with a method, method_a,
