On Wed, Feb 12, 2014 at 4:02 PM, Ethan Lowry wrote:
> Hi Cal, first off thanks for the detailed response.
>
> Regarding your second reply I'm not sure I understand the question? The
> csrf issue I described *is* the reason I was unable to use POST requests,
> which is what I originally wanted to
Hi Cal, first off thanks for the detailed response.
Regarding your second reply I'm not sure I understand the question? The
csrf issue I described *is* the reason I was unable to use POST requests,
which is what I originally wanted to do.
I will look in to all the options in the links posted an
On Wed, Feb 12, 2014 at 3:17 PM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:
> Hi Ethan, comments in-line;
>
>
> On Wed, Feb 12, 2014 at 1:41 PM, Ethan Lowry wrote:
>
>> Hi there,
>>
>> I have a bare-bones Django app set up and am planning on using the built
Hi Ethan, comments in-line;
On Wed, Feb 12, 2014 at 1:41 PM, Ethan Lowry wrote:
> Hi there,
>
> I have a bare-bones Django app set up and am planning on using the built
> in Django user auth to manage log in and registration via the Android app
> I'm developing.
>
> I've tried this a number of
>> Obviously this isn't an ideal or secure way of doing things and what I
originally tried was sending a POST request, but this gets denied with a
403 and a message about not having a CSRF cookie attached.
I haven't developed anything with Android but it sounds like you need to
send a CSRF in y
Hi there,
I have a bare-bones Django app set up and am planning on using the built in
Django user auth to manage log in and registration via the Android app I'm
developing.
I've tried this a number of ways and can, for example, log in by sending a
GET request such as ([url]/login?username=[us
6 matches
Mail list logo
