"destruk" wrote:
Just because you can doesn't mean you should -- if a get request string url is too long your server will lose data on the request. Apache will experience problems if your url length is longer than 4000 characters. Post data is limited to 8 megabytes by default.
Well obviously I'm not suggesting you use this method to post 8MB worth of data.
"destruk" wrote:
I just find it easier to code for without mixing and matching request types. Appending get variables to a post means you need to handle both on the other end - and definitely doubling them up sending the same variables both ways in the same request is inefficient.
You lost me here. Doubling them up? Doubling what up? I'll have to dig up that old thread. The tldr version is that there's literally no difference between using GET and POST with URL variables when using PHP to handle the request. None, zip, nothing. You can use identical PHP code and just change your GETs to POSTs or vice versa. As was brought up in that thread by EnTerr, a GET could be cached whereas a POST won't be, so if you're using GET to report something back to your server it could get "lost" along the way.
-JT
Roku Community Streaming Expert
Help others find this answer and click "Accept as Solution."
If you appreciate my answer, maybe give me a Kudo.
I am not a Roku employee.