> Many of the views are csrf protected, and the automated requests tsung
> generates don't get through the protection. For the moment I'm just
> commenting out the csrf middleware in settings.py, but this is
> obviously inconvenient.
>
I think you'll need to do some work with dyn_variable to pull the csrf
token out of the original form and re-inject it into the post you send
back. As far as I understand it, all that the csrf protection is is an
opaque value hidden in any form that needs to be present in the
submitted version to be valid. That stops "loose" posts from CSRF
attacks working as they don't know the magic key.
Malcolm
Thanks, this is a good clue. I'll try it out tomorrow and report back.
Best wishes
Ivan
--
============================================================
Ivan A. Uemlianin
Speech Technology Research and Development
iv...@llaisdy.com
www.llaisdy.com
llaisdy.wordpress.com
www.linkedin.com/in/ivanuemlianin
"Froh, froh! Wie seine Sonnen, seine Sonnen fliegen"
(Schiller, Beethoven)
============================================================
Glad that helped, and thank you for coming back with the working
settings for anyone else who runs into the same problem.
Malcolm