#124 closed defect (duplicate)
Better handling of raw POST data
Reported by: | Manuzhai | Owned by: | Adrian Holovaty |
---|---|---|---|
Component: | Core (Other) | Version: | |
Severity: | normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I'll come up with a patch for this, if slashzero doesn't.
Change History (4)
comment:1 by , 19 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 19 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
This was just discussed in IRC...
21:19 < slashzero> adrian_h: request.POST puts the raw data into one of the keys in the POST dict. That's ok until there is a equal sign 21:20 < adrian_h> slashzero: I'd be happy to fix if you provide a patch, or at least some example data, in a ticket 21:28 < manuzhai> slashzero: are you positive all well-behaving clients set the x-form-encoded thingie mimetype? 21:29 < manuzhai> if so, we could branch for that, then do the querydict parsing thing, and in the else just .read() whatever there is into some other request field
comment:3 by , 19 years ago
Component: | Admin interface → Core framework |
---|
comment:4 by , 19 years ago
Resolution: | → duplicate |
---|---|
Status: | reopened → closed |
Closing because patch is in #126.
Note:
See TracTickets
for help on using tickets.
I'm afraid there's not enough detail here to keep this open; if this is a valid issue please explain further what this means and reopen.