Hi Jerome,
> The choice of not exposing the query string and the fragment part of the
> target resource URI was deliberate.
The question is: is the question mark part of the query string?
> The reason is that the query string is often composed of a sequence of
> parameters ("key=value") that can appear in any order while keeping the same
> semantics.
Agreed. I wasn't trying to define a regexp on the request parameters, I was
just interested in catching the question mark. I wanted to differentiate
between '/accounts/123' and 'accounts?status=active'.
It turns out that attach("/account/[0-9]+",..) and attach("/accounts[.]+",...)
does the trick, but attach("/accounts?[.]+",...") would have been slightly more
elegant.
-Vincent.
