Timeline for Passing parameters to route
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 8, 2017 at 9:12 | comment | added | lordZ3d | @Clive I ended up using encoding the params and passing them via the Session, thanks. | |
| Dec 7, 2017 at 15:34 | answer | added | JHONATAN DAVID FERNANDEZ ROSA | timeline score: 0 | |
| Dec 7, 2017 at 12:38 | comment | added | Oulalahakabu | In which context/why don't you need params in url in this form ? I meant getting these params in post variables (instead of in query), and use hidden fields. If this is for security reason, that's not more secure... | |
| Dec 7, 2017 at 12:37 | comment | added | Clive♦ | passing them in Session is not really best practice - that's sort of correct, but only because best practice is typically to pass parameters in the URL or request body. If you don't want to use best practice methods, eliminating non best practice methods is going to leave you without any options :) Bottom line, if you want to get data from one page to another, but not allow the user to have access to that data, you need the session. Or two-way encryption. If you're doing this as any sort of security measure it'd be best not to bother, security through obscurity is all but pointless | |
| Dec 7, 2017 at 12:32 | comment | added | lordZ3d | @Oulalahakabu Can you give me an example of what you mean? | |
| Dec 7, 2017 at 12:23 | comment | added | Oulalahakabu | What about posting these parameters ? and get these in a Request object ? | |
| Dec 7, 2017 at 11:21 | history | asked | lordZ3d | CC BY-SA 3.0 |