On Sun, Oct 12, 2008 at 9:41 PM, Jan Koprowski <[EMAIL PROTECTED]> wrote: > > > > On Oct 12, 10:11 pm, "Jorge Vargas" <[EMAIL PROTECTED]> wrote: >> On Sun, Oct 12, 2008 at 6:45 AM, Jan Koprowski <[EMAIL PROTECTED]> wrote: >> >> > Hi ! >> >> > I am unsurprised to CSRF security generators. I can't find anywhere >> > secure_do_button. Last implementation is in rails module which is >> > deprecated. Any idea ? >> >> isn't that in html/secure_form.py ? > > I don't see anything: > > cd /usr/lib/python2.5/site-packages/WebHelpers-0.6.1-py2.5.egg/ > webhelpers > grep "secure_button_to" -r . > > ./rails/secure_form_tag.py:def secure_button_to(name, url='', > **html_options): > ./rails/secure_form_tag.py:__all__ = ['secure_form', > 'secure_form_remote_tag', 'secure_button_to'] > Plik binarny ./rails/secure_form_tag.pyc pasuje do wzorca > ./rails/urls.py: Creates the button_to html but leaves out the </ > form> to allow the secure_button_to() > ./rails/urls.py: > (webhelpers.rails.secure_form_tag.secure_button_to) to use this > function as well. > Plik binarny ./rails/urls.pyc pasuje do wzorca > [EMAIL PROTECTED]:/usr/lib/python2.5/site-packages/WebHelpers-0.6.1- > py2.5.egg/webhelpers#
Jon Rosebaugh wrote secure_form.py. I'm not sure if the missing secure_button_to was an oversight or if we thought it was part of the Javascript-heavy functions (link_to_remote and secure_form_remote_tag) which were also not ported. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
