nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Skora <jsk...@gmail.com>
Subject Re: Jetty request filtering of NiFI API requests
Date Wed, 01 Jun 2016 13:58:37 GMT
Matt,

That looks like what I'm looking for.

I haven't looked at how the web.xml pieces get put together, can I package
it separately so it can hot deploy or does it need to be baked into the
framework?

Thanks
JoeS

On Tue, May 31, 2016 at 3:26 PM, Matt Gilman <matt.c.gilman@gmail.com>
wrote:

> Joe,
>
> There is no extension point for loading REST API mappings. However, we have
> added a filter for doing this to support the upcoming NiFi 1.0.0 where the
> site to site endpoint will be updated. This PR [1] shows the filter, how
> it's wired up, and how it's tested. Thanks.
>
> Matt
>
> [1] https://github.com/apache/nifi/pull/422/files
>
> On Tue, May 31, 2016 at 2:43 PM, Joe Skora <jskora@gmail.com> wrote:
>
> > I have a legacy system that makes requests against the NiFi API, but some
> > requests don't come in quite right.  In lieu of changing the legacy
> system,
> > it would be great if I can create a Jetty request filter that 1) corrects
> > the URL path and 2) changes or removes some header values.
> >
> > First, can this be done?  It looks like it, but I haven't found any
> > examples that do the specific changes I need.
> >
> > Second, if possible, how does this filter need to be wired into the NiFi
> > web application?  It would be ideal if this filter could be packaged in a
> > Nar and deployed, but if that's not possible how does it need to be wired
> > into the web-app filter chain?
> >
> > Any help is greatly appreciated.
> >
> > Regards,
> > JoeS
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message