Also looks like the TLDs don't include the internationalized country code top level domains, only the test ones.
On Wednesday, March 27, 2013 2:57:00 PM UTC-7, Derek wrote: > > It should be checking against RFC 3986, not RFC 2396. > > On Wednesday, March 27, 2013 11:44:08 AM UTC-7, Jonathan Lundell wrote: >> >> On 27 Mar 2013, at 11:25 AM, Lamps902 <[email protected]> wrote: >> >> It seems that every once in a while, the IS_URL validator doesn't want to >> accept a URL that's valid. For example, I believe the ^ character prevents >> IS_URL from accepting something like >> http://finance.yahoo.com/q/hp?s=^IXIC+Historical+Prices<http://finance.yahoo.com/q/hp?s=%5EIXIC+Historical+Prices>. >> >> Is there a parameter to permit IS_URL to accept certain special characters, >> or that makes the validator 'less strict', so that it can accept URLs such >> as the one above? Thanks. >> >> >> >> IS_URL first checks the URL against RFC 2396, which requires '^' to be >> escaped. I don't see a way to override it; better to URL-escape your URLs. >> > -- --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
