Hi, > While code is planned to run under register_globals=off, it could also > be interested to differenciate POST (which implies changes on the > server) and GET (which implies no changes will be made).
Yes but your "differences" between POST and GET are not completely correct , the difference between POST and GET are just the possible length sent to the server. GET sends the data as QUERY data in the request and POST sends data independently and including a Content-Length header. For more information check the HTTP 1.1 protocol RFC ( and after check the foo rfc :) In addition , we can have more clean code ( about 4/5/6 lines when not differenciating between GET and POST and 2/3 whe differenciating which method is used for set the variable values ) so i will check soon to change the current code i have made in my branch and then set up new code ( more clean and short ) to handle variables by method as they are sent to the script. > Browsers support POST well and warn the user that data will be reposted > when (s)he clicks on 'Back'. > I remember having a comment posted twice in a support request after > using my browser's history. Handling GET and POST well would avoid that > issue. However, I am not sure how I managed to have my comment posted > twice, since posting a comment requires using a FORM with the POST > method... I've seen that every form in /frontend/php/news use POST. Best regards to the rest of developers! Have nice time ( i am getting holidays for 11 days ) .
