Re: Parsing unnamed parameters from urls

> Matches letters, digits and underscores. Equivalent to [A-Za-z0-9_]. I suppose that is a good enough definition. according to the docs: > Match a word character. Word characters are > [\p{Alphabetic}\p{Mark}\p{Decimal_Number}\p{Connector_Punctuation}\u200c\u200d].

Re: Parsing unnamed parameters from urls

I'll try it, but the cheat sheet I was using said that w Matches letters, digits and underscores. Equivalent to [A-Za-z0-9_]. On Mon, Oct 17, 2016 at 8:45 PM, Keisuke Miyako wrote: > would it not be safer to specify > > [^/]* = "anything but a forward slash" > > instead

Re: Parsing unnamed parameters from urls

For a different take, here's the old school version I get to parse URL items into an array: // WebRequest_ParseURLItems // Strip parameters off URL and parse the remainder into items. // 4D automatically URL decodes the incoming data before it arrives. // Otherwise, this routine would need to

Parsing unnamed parameters from urls

I'm working on an api server and needed a way to grab parameters from the url by their placement. i.e., from "/api/people/uuid/" I want the table name and the uuid. If I received /api/?table=people=uuid then 4D's Web Get Variables would work just fine. So, I came up with this (cribbed from