If you're interested in some piecemeal work, I could use some help. mike at
mzoo.org.
On Friday, June 17, 2022 at 3:10:16 PM UTC-5 181...@northsouth.edu wrote:
> I have basic to intermediate knowledge on Django, but don't find any entry
> level job to master my django knowledge in my country, c
I have basic to intermediate knowledge on Django, but don't find any entry
level job to master my django knowledge in my country, can any one suggest
me where I can get some project or industry level job in django , please. I
am badly need that
On Friday, June 17, 2022 at 11:29:04 PM UTC+6 Mike
That sounds hopeful. Where do you put that config? Settings.py?
On Friday, June 17, 2022 at 12:25:29 PM UTC-5 vicker...@gmail.com wrote:
> I was having a similar issue after setting up https with certbot. After
> searching around, I found adding this to settings worked.
>
> CSRF_TRUSTED_ORIGINS
I was having a similar issue after setting up https with certbot.
After searching around, I found adding this to settings worked.
CSRF_TRUSTED_ORIGINS = ["https://yourdomain.com";, "https://www.yourdomain.com";]
I'd be curious to hear from others, because I'm *not *an expert in how
to best set up
Html form like action form use
On Fri, Jun 17, 2022, 21:23 Mike Kilmer wrote:
> By the way, using Django 4.0.
>
> Thanks, Rahul.
>
> I believe this is a default Django template, and wouldn't the fact the the
> page/form creates a cookie be a sign that that action triggered by `{%
> crsf_token %}
{% crsf_token %} use this action form down
On Fri, Jun 17, 2022, 20:47 Mike Kilmer wrote:
> Hi.
>
> I'm fairly new to Django. Here's what I need insight on:
>
> Local server, no issue.
>
> On production: CSRF 403 error on login.
>
> There's a cookie loaded on the login page containing
Hi.
I'm fairly new to Django. Here's what I need insight on:
Local server, no issue.
On production: CSRF 403 error on login.
There's a cookie loaded on the login page containing csrftoken:
pAFeeUI8YFXZ2PKRYxOTX1qz4Xgto42WVNi7FFvBlZDqcFLwQ2rdQvVeZBHFSpLW
(Local and Session stor
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
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 p
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
fixed. thanks mate!
On Thursday, June 14, 2012 3:46:24 AM UTC-4, cmac0tt wrote:
>
> I feel like an idiot here, I've worked my way around this multiple times
> but its just not working this time and as you can see ive thrown every
> method there is in the documentation at it.
>
> (note that I am
On Thursday, 14 June 2012 10:00:09 UTC+1, cmac0tt wrote:
>
> ahem, so here is the view
>
> from wikicamp.wiki.models import Page
> from django.shortcuts import render_to_response
> from django.http import HttpResponseRedirect
> from django.shortcuts import render
> from django.shortcuts import redi
ahem, so here is the view
from wikicamp.wiki.models import Page
from django.shortcuts import render_to_response
from django.http import HttpResponseRedirect
from django.shortcuts import render
from django.shortcuts import redirect
from django import forms
import htmllib
from django.template import
ok, so this is my view now. Maybe I'm not understanding and if so I
apologize. We all start somewere right. I just dont know why I'm having
trouble with it now when I had it working last time around with simply
using C {}
On Thursday, June 14, 2012 3:46:24 AM UTC-4, cmac0tt wrote:
>
> I feel
On Thursday, 14 June 2012 08:46:24 UTC+1, cmac0tt wrote:
>
> I feel like an idiot here, I've worked my way around this multiple times
> but its just not working this time and as you can see ive thrown every
> method there is in the documentation at it.
>
> (note that I am learning python and djan
I feel like an idiot here, I've worked my way around this multiple times
but its just not working this time and as you can see ive thrown every
method there is in the documentation at it.
(note that I am learning python and django right now on the fly) however
here is my views, the form with th
Hi Russ,
That's a great suggestion. I did add csrf tokens in all templates involved,
but still got the problem. Thsi makes me wonder whethere or not there is
somethign in django-forum's internals that causes the template system to
throw a fit even with the tags and middleware available.
Will look
On 14 ?.?. 2010, at 18:06, Sithembewena Lloyd Dube wrote:
> Hi Jonathan,
>
> Thanks for the tip. The rub with that is, we are using csrf tokens in the
> rest of our views. While authentication may still take care of basic
> security, removing csrf middleware would surely increase XSS risk?
Ye
Hi Jonathan,
Thanks for the tip. The rub with that is, we are using csrf tokens in the
rest of our views. While authentication may still take care of basic
security, removing csrf middleware would surely increase XSS risk?
2010/10/14 Jonathan Barratt
> On 14 ?.?. 2010, at 16:58, Sithembewena Ll
On Thu, Oct 14, 2010 at 5:58 PM, Sithembewena Lloyd Dube
wrote:
> Hi all,
>
> I just installed django-forum (http://code.google.com/p/django-forum/) in my
> Django 1.2.3. project and all went well (admin) until I got CSRF errors
> while trying to load a new forum I created in the admin.
> I added
On 14 ?.?. 2010, at 16:58, Sithembewena Lloyd Dube wrote:
> Hi all,
>
> I just installed django-forum (http://code.google.com/p/django-forum/) in my
> Django 1.2.3. project and all went well (admin) until I got CSRF errors while
> trying to load a new forum I created in the admin.
> I added @cs
Hi all,
I just installed django-forum (http://code.google.com/p/django-forum/) in my
Django 1.2.3. project and all went well (admin) until I got CSRF errors
while trying to load a new forum I created in the admin.
I added @csrf_protect tags to the forms of the pages concerned and also made
sure to
Depends on what you have for your render_to_response. It's pretty good
practice (from what I can tell) to use something like this
Note that response is a dict that has my per view context variables in
it.
return render_to_response("myapp_super_cool_template.html", response,
context_instance=Reque
I am new to Django and loving it. I am using v1.2 locally and have an issue
with my first project from scratch: The CSRF token is not being sent with
my form post. I have {% csrf_token %} inside the tag and have
verified that a csrf cookie does exist for the browser. However, I get the
error m
27 matches
Mail list logo
