#2030 closed defect (wontfix)
When hitting a problem with an upload the DEBUG screen will display full file contents
Reported by: | Owned by: | Adrian Holovaty | |
---|---|---|---|
Component: | Core (Other) | Version: | dev |
Severity: | normal | Keywords: | upload |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Currently when you are testing file uploads and you hit a problem you will get a DEBUG screen which will have your FileField data in the debugging information. The only downside is that if you have a file of, say, 5 MB, the DEBUG screen will show all 5 MB of that data in the appropriate dict value for the FileField key.
This is not what you would want to see because it in general will slow your browser down considerably.
Perhaps this can be stripped/masked out before dumping into the DEBUG screen.
Change History (3)
comment:1 by , 18 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 by , 18 years ago
How about setting up the DEBUG screen to truncate any value that's longer than 2000 characters? That would solve this problem without needing a special case for file upload fields.
I don't think this one is worth fixing, because it'd be hard to target
FileField
s in the debug output. We're already explicitly *not* displayingrequest.FILE
in the debug output.