This is the name of a filter (not a rule)
> >
> >
> >
> >...This has to be globally unique,
> >. since all filters are combined together
> > .
&g
defined elsewhere
> .
> .
> This matches a string in the content that the parser has
> tokenized out (e.g., the URL in the content, such as href
> attribute) it's a regular expression. Unsure how this
>
rom the mailing list (although, that
looks like a 'blog' entry, so maybe we should copy and update a
non-dated location? - probably
https://knox.apache.org/books/knox-0-14-0/dev-guide.html#Rewrite+Provider )
Regards,
Nick
____
From: larry mccay [lm
Hi Stuart -
At first glance, it seems to look okay.
I am wondering whether you are just running into the difficult dance of
what you need to do to get the service definitions changes updated.
I believe that you will find that you need to do the following when you
iterate over changes in rewrite
Using Knox 0.11 and reproduced with Knox 0.14, we're having trouble
getting basic URL rewriting to work. The real problem is with an
ExpressJS application, and the URL is part of some JavaScript, but I
wanted to get this basic example working first. Please may I ask for
help to spot what I'm doing
