Closed
Bug 686374
Opened 14 years ago
Closed 14 years ago
Possible security issue with ExtendedURLField
Categories
(Input Graveyard :: Code Quality, defect)
Input Graveyard
Code Quality
Tracking
(Not tracked)
RESOLVED
FIXED
4.2
People
(Reporter: davedash, Unassigned)
Details
(Whiteboard: [upstream][qa-])
Check that verifies_true=False in usage of ExtendedURLField.
|
Reporter | |
Comment 1•14 years ago
|
||
Sorry it should be:
verify_exists=False
|
|
Reporter | |
Comment 2•14 years ago
|
||
I'm lazily blocked on James Bennet's patches to the 1.3x (and presumably 1.4x) branches... If there's a rush on this, I can manually change things and revert Input to 1.3. But I don't think there is a rush.
Whiteboard: [upstream]
|
|
Reporter | |
Comment 3•14 years ago
|
||
These got fixed.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
|
||
Updated•14 years ago
|
Whiteboard: [upstream] → [upstream][qa-]
|
Assignee | |
Updated•9 years ago
|
Product: Input → Input Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•