Timeline for answer to Passing arrays as url parameter by nash
Current License: CC BY-SA 2.5
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 17, 2023 at 20:08 | history | edited | Community Bot |
replaced http://nl3.php.net with https://www.php.net
|
|
| Mar 9, 2015 at 13:29 | comment | added | Mikko Rantalainen | You really should not pass untrusted data to unserialize(). Try json_encode() and json_decode() instead. | |
| Nov 20, 2009 at 8:29 | comment | added | uji | the max size of the GET parameter was what i was worried about thats why i was (stupidly) hoping that the parser wont mind if its an array that is passed. i realized just now that it wont work without touching the max size. Thanks anyway nash, I think i will be doing it with sessions | |
| Nov 19, 2009 at 16:15 | comment | added | Kzqai | Yeah, serialize isn't really a clean way of doing things when you're working with urls, because it expands the data so much. Better to go custom. | |
| Nov 19, 2009 at 14:26 | comment | added | knittl | serializing is also a nice way of doing it, but then it's in a not-so-readable form anymore | |
| Nov 19, 2009 at 14:23 | history | answered | nash | CC BY-SA 2.5 |