rfellows commented on issue #211: NIFIREG-295 Add support for proxying via
Apache Knox
URL: https://github.com/apache/nifi-registry/pull/211#issuecomment-521975301
@ijokarumawak Thanks! I knew there had to be something I was missing.
rfellows commented on issue #211: NIFIREG-295 Add support for proxying via
Apache Knox
URL: https://github.com/apache/nifi-registry/pull/211#issuecomment-521862747
> Thank you very much @rfellows ! Using hash makes everything clean! I'm
also +1 with that approach. Rebased with the latest
rfellows commented on issue #211: NIFIREG-295 Add support for proxying via
Apache Knox
URL: https://github.com/apache/nifi-registry/pull/211#issuecomment-521759290
> @rfellows @mcgilman Do you have any solution to handle this? A possible
one would be changing how webpack inject the
rfellows commented on issue #211: NIFIREG-295 Add support for proxying via
Apache Knox
URL: https://github.com/apache/nifi-registry/pull/211#issuecomment-521204689
> Registry works fine behind Knox. Deeplinks work fine, too. But still
seeing following warning messages on browser console.
rfellows commented on issue #211: NIFIREG-295 Add support for proxying via
Apache Knox
URL: https://github.com/apache/nifi-registry/pull/211#issuecomment-520872945
> > @rfellows do you have any advice on this behavior? (where to look at ...
etc) Also, the way I changed absolute paths to
rfellows commented on issue #211: NIFIREG-295 Add support for proxying via
Apache Knox
URL: https://github.com/apache/nifi-registry/pull/211#issuecomment-520805796
> @rfellows do you have any advice on this behavior? (where to look at ...
etc) Also, the way I changed absolute paths to
rfellows commented on issue #211: NIFIREG-295 Add support for proxying via
Apache Knox
URL: https://github.com/apache/nifi-registry/pull/211#issuecomment-520804633
> * Would you please share exact maven commands to run backend api and
frontend UI separately??
1. Build the whole
