From: gilberto d. s. a. <gs...@gm...> - 2014-01-24 02:44:28
|
IMO is that customer, customer branch and vendors must have same validation, alfanumeric and hifen char (-) and undercore char (_). this help all of us for url (get and post) and urlencode/urldecode. many functions on php, python, xml and api already have these constraints. reference [1] et ali. See http get processing, example: http://weberp.brasil.com.br/Customers.php?customercode=xxxxxxxxx If in this hypotetical case code xxxxxxxxx have some special char we must use aditional urlencode/urldecode for http server handle it. regards! [1] http://us3.php.net/manual/en/function.urlencode.php<http://us3.php.net/manual/pt_BR/function.urlencode.php> 2014/1/23 ExsonQu <hex...@gm...> > *Hi, Richard,* > > Thank you for your report! > > The validation pattern in client side is just try to keep > consistent with server side validation. If you've passed the client side > validation. The server side still will catch the illegal chars. > > So the question is that shall we add this validation to > Customers.php script to keep the consistency with CustomerBranches.php ? > > Thanks and best regards! > > Exson > > > > -- > View this message in context: > http://weberp-accounting.1478800.n4.nabble.com/Inconsistency-in-Customer-branch-codes-tp4657184p4657186.html > Sent from the web-ERP-developers mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil |