Re: Redirect GET to POST

Then don't you just redirect back to the return url? That's not your job to
post that data as the authenticating agency. Your app that is the recipient
of the redirect can issue auth tokens on a GET. That's not something that
requires a POST.

Joseph

On Tue, Jun 13, 2017 at 2:05 PM Aaron Dalton <[email protected]>
wrote:

> That sounds so nefarious! But yes, in the one single case where it's the
> official, sanctioned front end accessing the API, I want to save the click.
> The front end is a single-page app hosted on a completely different
> machine. But the API is also accessible to third-party developers.
>
>
> On Tuesday, 13 June 2017 11:38:36 UTC-6, Joseph Tate wrote:
>>
>> So you want to bypass the user's consent?
>>
>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "cherrypy-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cherrypy-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
> To post to this group, send email to cherrypy-users-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
> Visit this group at https://groups.google.com/group/cherrypy-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
To post to this group, send email to cherrypy-users-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
Visit this group at https://groups.google.com/group/cherrypy-users.
For more options, visit https://groups.google.com/d/optout.