Yup. I glossed over that. Thanks Nii Amon
Steve Vinoski wrote: > On 10/13/08, nii amon <[EMAIL PROTECTED]> wrote: > > > > OK I "fixed" this. > > > > For some reason, when I do: > > > > yaws_api:queryvar(A, "username"), > > > > erlyweb or yaws throws up about a badmatch. I thought that must have > > been because the input was not in the yaws arg passed to the function > > but a parse_post test I did showed that it was indeed in there. What I > > did was to do a yaws_api:parse_post(A) and then use lists:keysearch to > > pick up the relevant inputs. > > > > Did I miss something here? How do people pick up POST parameters from > > a request? > > This page explains that the queryvar(A, "key") form is applicable only > to the query portion of the URL: > > <http://yaws.hyber.org/query.yaws> > > If you want code that covers both the query portion of the URL as well > as POST data, then you got it right -- call yaws_api:parse_query(A) to > get a property list, and then use lists:keysearch, proplists:lookup or > proplists:get_value to look through it. > > --steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" 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/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
