Task #35090
Evaluate base64_encoding of URI-transferred serialized objects
| Status: | New | Start date: | 2012-03-21 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Sprint: | Has patch: | No | ||
| PHP Version: | Complexity: | |||
| Votes: | 0 |
Description
At least Fluid-Widgets add a serialized object to links in order to transfer them across requests.
Maybe it's considerable to base64-encode these serialized objects to avoid problems like the suhosin's null-byte-omission.
History
Updated by Adrian Föder about 1 year ago
- Assignee set to Bastian Waidelich
Updated by Bastian Waidelich 9 months ago
- Assignee deleted (
Bastian Waidelich)
Mh, base64 encoding sounds a bit "expensive" to me, but I can't really judge this atm.
I unassign myself for now so someone else can comment on this