#10034: FormWizard has a security_hash check failure with Textareas with
leading/trailing newlines in Safari
-----------------------------------------------+----------------------------
 Reporter:  danaspiegel                        |       Owner:  nobody    
   Status:  new                                |   Milestone:            
Component:  django.contrib.formtools           |     Version:  1.0       
 Keywords:  security_hash textarea formwizard  |       Stage:  Unreviewed
Has_patch:  0                                  |  
-----------------------------------------------+----------------------------
 I have a Form with a TextField, and when I put this form into a
 FormWizard, the security_hash generated for that form is different
 before/after the next form is submitted. This only happens on Safari. I've
 traced the issue to a TextField that has leading and/or trailing newlines.

 In Firefox, a Textarea is apparently stripped upon submission, but in
 Safari, the leading/trailing newlines are submitted. As a result, when
 submitting the form with the Textarea, the security_hash that is generated
 uses the value of the field with the newlines included. But when I submit
 the next form, the security_hash that is generated from the previous
 fields doesn't have the newlines in that field's value. As a result, the
 security_hash is different, generating a security_hash failure. This may
 be due to the way that the previous fields are rendered into the second
 form.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10034>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to