You can avoid using those functions, you can do something like this
pattern=“{scheme}://{host}:{port}/{gateway}/{topology}/myapp?originalUrl={originalurl}&{**}"/>
>
>template="{$frontend[url]}/myservice/myapp?originalUrl=/{gateway}/{topology}/{originalurl}&{**}"/>
The prefix, postfix are
Hi Sandeep,
Unfortunately that function is only available in 1.10 or 0.13 or later which I
don’t have access to. Do the $postfix, $prefix, and $infix also work with
frontend ‘path’ instead of ‘url’?
Regards,
Christopher Jackson
> On Jul 27, 2018, at 2:16 PM, Sandeep Moré wrote:
>
> It shoul
It should be possible using parameterized rewrite variables, this is an
example from Spark History rewrite rules
or in the above example
Best,
Sandeep
On Fri, Jul 27, 2018 at 1:03 PM Christopher Jackson <
jackson.christopher@gmail.com> wrote:
> Hi All,
>
> Curious
Hi All,
Curious if it is possible to rewrite a query parameter value to append a string
to the original value? I tried the below configuration but I don’t think its
valid as requests to the resource were just hanging.
Entry from service.xml for the particular path:
Entries in rewrite.xml:
Well, it seems that you can certainly specify IPv6 using curl for a call to
webhdfs as the following output shows:
new-host-6:knox-1.1.0 lmccay$ curl -ivk6u guest:guest-password
https://localhost:8443/gateway/sandbox/webhdfs/v1/tmp?op=LISTSTATUS
* *Trying ::1*...
* TCP_NODELAY set
** Connected t
Hello,
Can Knox work on IPv6 interface? Specifically, I want to have Client/User to
Knox communication on IPv6 network but my backend services say Ambari/WebHDFS
runs on IPv4 network so I want Knox to Service communication on IPv4 network.
Will this work with Knox ?
Thanks & Regards,
Rajat
