> Akimoto, > > You really need to read up on HTTP and the difference between Query > Parameters and Body Parameters. It will help you write better > applications.
Hello, J, Good evening. Yes, you're very right and I have been referring to documentation on search.cpan.org especially the catalyst tutes, J Rockway's book and Catalyst::Request documentation. Yes, reading the Catalyst::Request documentation, I was aware that $c->request->params was a combination of both query and body parameters. Are you able to provide us with a good example of the usefulness of getting parameters from both query and body? I thought it would be neater to take the parameters from either one source only (not both ). Can you please recommend some documentation related to HTTP and the difference between Query Parameters and Body Parameters? I googled with 'HTTP and the difference between Query Parameters and Body Parameters.' but didn't get anything interesting. > If you simply change your form tag to be <form method="post" > action=" > http://lginsurance.com.au/subscriptions/edit";> there will be no > query > parameter present. > > You most certainly have the action set to " > http://lginsurance.com.au/subscriptions/edit?id=3389";, which is what > is > populating the GET parameter. Yes, I made the change here and problem solved. I understand what you and Sebastian Willert mean now. I made sure that my form had an action of 'http://lginsurance.com.au/subscriptions/edit' (without "?id=3389") and it works beautifully. It now knows that it has to call my controller, sub edit which accepts requests of path, '/subscriptions/edit'. Thank you for your time, J! K. akimoto > > -Jay > _______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
