Re: cURL or wget with contrib.auth and CSRF

2014-12-05 Thread Collin Anderson
Hi David, It's actually pretty easy in curl. curl -d"csrfmiddlewaretoken=a" -H"Cookie: csrftoken=a" http: //yourdjangosite.com Collin On Thursday, April 14, 2011 7:32:46 AM UTC-4, David wrote: > > Hello, > > I am sorry for asking this, I know similar questions have been asked > before but I

Re: cURL or wget with contrib.auth and CSRF

2014-12-04 Thread Kevin Trainor
David, I realize this was a long time ago, wondering if you ever got it working. I'm battling the same dragon currently. Step 1: seems to work wget --save-cookies c:\cifs\cookies.txt --keep-session-cookies --no-check-certificate --http-user=myuser --http-password=mypass

Re: cURL or wget with contrib.auth and CSRF

2011-04-14 Thread Shawn Milochik
This isn't a Django question. Check out the man pages for curl and wget -- both have the ability to GET & POST and retain cookie data for future requests. You shouldn't have to change anything in Django. -- You received this message because you are subscribed to the Google Groups "Django

cURL or wget with contrib.auth and CSRF

2011-04-14 Thread David
Hello, I am sorry for asking this, I know similar questions have been asked before but I could not piece together the answer I needed from previous contribution! I have a view, for example: @login_required def clever_view(request): #Render a PDF to a string response =