On Monday, August 4, 2014 7:08:11 AM UTC-7, Rémy Reche wrote: > > I agree with you, but it is web2py (gluon) which process the arguments. > This error occurs before entering my function. > > > On Friday, August 1, 2014 9:27:47 PM UTC+2, Derek wrote: >> >> Well, before you process the arguments, you would want to encode it as >> utf-8. See here: >> https://groups.google.com/forum/#!msg/web2py/B_EOmprbjO0/kMEHiiCrmYEJ >> >> URLs get converted into punycode if they are not ascii, so that wouldn't >> be an issue. >> >
Do you need to make sure the client code is using unicode when it builds the URL (and/or POST data) before it ships it to you? Do you control the client code, or is it third-party software that you are having point to you? /dps > >> On Thursday, July 31, 2014 2:33:56 AM UTC-7, Rémy Reche wrote: >>> >>> I am using the decorator @request.restful() in order to implement a >>> rest API. Unfortunatly, one on my function take an argument which can >>> contain non-ascii character, for instance 'Gymnase Joseph Guétat'. Each >>> request using this string returns a web2py error with the following >>> comment: invalid arg <Gymnase Joseph Gu\xc3\xa9tat>. Is this an issue with >>> the url encoding/decoding mechanism ? a routing issue ? How can I solve >>> this problem ? >>> >>> Thanks, >>> >>> Rémy >>> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
