Hello Abraham V.
Thank you for replying.
It is nice idea.
But, PC version also sometimes happened. less than Mobile
2015年1月8日木曜日 20時09分11秒 UTC+9 Abraham Varricatt:
>
> Can it be possible that you are rendering a different template (without
> CSRF) for the mobile version?
>
> -Abraham V.
>
>
> On Thursday, January 8, 2015 2:15:21 PM UTC+5:30, Sugita Shinsuke wrote:
>>
>> Hello Vijay Khemlani
>>
>> Thank you for replying.
>> But, of cause I appended the tag in my form like below
>>
>> <div class="container">
>> <form method="POST" action=".">{% csrf_token %}
>>
>> but I wonder about that using the iframe is bad.
>>
>> The form is child of iframe.
>>
>> I also checked Chrome's developer tool.
>> The csrf token was saved in the cookie.
>>
>> 2015年1月6日火曜日 23時00分10秒 UTC+9 Vijay Khemlani:
>>>
>>> ¿Did you include de {% csrf_token %} tag in the form? ¿Is it generating
>>> the corresponding hidden input tag in the html?
>>>
>>> On Tue, Jan 6, 2015 at 6:09 AM, Sugita Shinsuke <[email protected]>
>>> wrote:
>>>
>>>> Hello.
>>>>
>>>> When I use Django via my smart phone Android and iOS.
>>>> The error sometimes occurred.
>>>>
>>>> Forbidden (403)
>>>> CSRF verification failed. Request aborted.
>>>> Help
>>>> Reason given for failure:
>>>> CSRF token missing or incorrect.
>>>>
>>>> In general, this can occur when there is a genuine Cross Site Request
>>>> Forgery, or when Django's CSRF mechanism has not been used correctly. For
>>>> POST forms, you need to ensure:
>>>> Your browser is accepting cookies.
>>>> The view function uses RequestContext for the template, instead of
>>>> Context.
>>>> In the template, there is a {% csrf_token %} template tag inside each
>>>> POST form that targets an internal URL.
>>>> If you are not using CsrfViewMiddleware, then you must use csrf_protect
>>>> on any views that use the csrf_token template tag, as well as those that
>>>> accept the POST data.
>>>> You're seeing the help section of this page because you have DEBUG =
>>>> True in your Django settings file. Change that to False, and only the
>>>> initial error message will be displayed.
>>>> You can customize this page using the CSRF_FAILURE_VIEW setting.
>>>>
>>>> I append django.middleware.csrf.CsrfViewMiddleware', of
>>>> MIDDLEWARE_CLASSES in settings.py
>>>>
>>>> I use
>>>> Python 2.7.5
>>>> Django 1.6.4
>>>>
>>>> Anyone who know this matter, please help.
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Django users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To post to this group, send email to [email protected].
>>>> Visit this group at http://groups.google.com/group/django-users.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/django-users/e0db1d43-8897-40fc-be1d-65c76d9da503%40googlegroups.com
>>>>
>>>> <https://groups.google.com/d/msgid/django-users/e0db1d43-8897-40fc-be1d-65c76d9da503%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/7a15bacb-ffbf-46c2-aa9f-e3a2e6fc88be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
