On Sat, Oct 16, 2010 at 10:34 PM, sibande <[email protected]> wrote: > I have a keyword that is available both on GET and on POST (/search? > word=webpy and post data word=python).
That sounds like bad design. Why would you use both GET and POST for the same thing? If it's a search, it'd be more logical to stick to GET and enforce that by raising badrequest on POST. -- Branko Vukelić [email protected] [email protected] Check out my blog: http://www.brankovukelic.com/ Check out my portfolio: http://www.flickr.com/photos/foxbunny/ Registered Linux user #438078 (http://counter.li.org/) I hang out on identi.ca: http://identi.ca/foxbunny Gimp Brushmakers Guild http://bit.ly/gbg-group -- You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/webpy?hl=en.
