That worked. I was not aware of the csrf exempt directive.
My email form works the way that I want. On Friday, August 28, 2015 at 5:22:46 PM UTC-4, pythonista wrote: > > > > I have created a form that works fine for GETS and POSTS through the > browser. > > I have embedded the form with a GET (action) in the email, and the data > gets transferred to the server as expected. > > The email POST looks like it needs a csrf token. > Is there anyway to generate this and embed it on the fly as hidden? > > What are the best practices for capturing and submitting form data from > emails. > POST or GET > > In my case the data is not sensitive information. > > > Thanks in advance > -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. 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/1a304990-7883-4be9-9185-dc133b567392%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
