- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Unable to stop nifi processor in test environment finding the prod request url in network tab, please let me know how to fix/stop the processors, facing issue only in test environment.
- Labels:
-
Apache NiFi
Created ‎08-01-2021 11:29 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unable to stop nifi processor in test environment finding the prod request url in network tab, please let me know how to fix/stop the processors, facing issue only in test environment.
Geetin below alert/response when trying to stop the processor(facing same issue for all the processor's).
Response in console:
Mixed Content: The page at 'https://url.......test.ziprealty.com/nifi/?processGroupId=root&componentIds=91d5d6ca-3a68-35cd-96a0-...' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http:url..........aur.ziprealty.com/nifi-api/processors/91d5d6ca-3a68-35cd-96a0-8dabeb405b22'. This request has been blocked; the content must be served over HTTPS.
send @ jquery.min.js:4
ajax @ jquery.min.js:4
n @ nf-canvas-all.js?1.7.0:50
(anonymous) @ nf-canvas-all.js?1.7.0:50
each @ d3.min.js:2
stop @ nf-canvas-all.js?1.7.0:50
S @ nf-canvas-all.js?1.7.0:38
(anonymous) @ nf-canvas-all.js?1.7.0:38
dispatch @ jquery.min.js:3
$event.dispatch @ jquery.event.drag-2.3.0.js:380
q.handle @ jquery.min.js:3
Please help to resolve the issue.
Thanks.
Created ‎08-05-2021 12:13 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@sivag
Did you recently upgrade your browser?
Have you tried using a different browser?
Created ‎08-10-2021 06:59 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@MattWho Thanks for reply, I have not upgraded the browser and tried with different browser's, getting same issue and which was working pipeline also getting same issue now.
