Thanks much for the help - despite reading it a few times, I overlooked
this before in the reference docs.   The stick table is a great feature.

Willy -- thanks for your comment on double-posting to Serverfault and here.
 I didn't get a response on Server Fault, so I moved my question over to
the user list.  I think it's helpful to have that message stay live (I'll
"accept" your answer that the response so that it's clear it is resolved).
 Thanks again.

Best, WILL



On Fri, Apr 5, 2013 at 12:12 PM, Baptiste <[email protected]> wrote:

> Will,
>
> I'm just curious what you can't understand in the current
> documentation, which is, as a remeinder:
> --------------8<----------------------
> url_param(<name>[,<delim>])
>              This extracts the first occurrence of the parameter <name> in
>              the parameter string of the request and uses the corresponding
>              value to match. Optionally, a delimiter can be provided. If
> not
>              then the question mark '?' is used by default.
>              A typical use is to get sticky session through url for cases
>              where cookies cannot be used.
>
> Example :
> # match http://example.com/foo?PHPSESSIONID=some_id
> stick on url_param(PHPSESSIONID)
> # match http://example.com/foo;JSESSIONID=some_id
> stick on url_param(JSESSIONID,;)
> --------------8<----------------------
>
> I can't see how much simpler I could have done it.
> Any feedback and thought is welcome!
>
> Baptiste
>
>
> On Fri, Apr 5, 2013 at 8:19 AM, Willy Tarreau <[email protected]> wrote:
> > On Thu, Apr 04, 2013 at 12:24:48PM -0700, Will Glass-Husain wrote:
> >> Thanks!
> >>
> >> That worked great.  I'm using dev17, but I'll upgrade to 18.
> >>
> >> Why is the comma needed before the semi-colon?
> >
> > It's the argument delimiter. Argument 1 is the param name, argument 2 is
> > optional and is the delimiter.
> >
> >> A blog entry would be great - the documentation was not very detailed
> >> around this.
> >
> > Feel free to improve it :-)
> >
> > BTW, I have a comment to make, it is a bit counter-productive to post
> > a question both on serverfault and here, because it's likely that
> > people will have to do the work twice. Either you post it here, or on
> > serverfault. If you post to stackoverflow, just post a link here and
> > not the detailed question otherwise what happens is exactly this :
> someone
> > responds here on the list and nobody updates the question on serverfault.
> >
> > Willy
> >
>



-- 
Forio Online Simulations

Will Glass-Husain
415 440-7500x89
[email protected]
www.forio.com

Reply via email to