Hello Robert,
It could be that your monitored application is HTTPS and the connection to AXA is only HTTP (if on-premise). If that is the case, you would need to put a load balancer in front of AXA, or more specifically route the traffic to AXA through the load balancer (which would also handle the HTTPS part as there is no native HTTPS support in AXA)
This is part of enhanced browser security to not allow mixed HTTPS and HTTP, here's the first link I could find on it.
https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content/How_to_fix_website_with_mixed_contentOtherwise it's possible that the application itself does not expect requests to hosts that it does not recognise, perhaps some sort of traffic management not allowing the request to the AXA server so it may be necessary to whitelist requests to the AXA server.
Many thanks,
David
Original Message:
Sent: 08-29-2019 06:26 AM
From: Robert Wadra
Subject: AXA snippet issue
Hi Team,
Using the latest version of AXA, I am having issues while onboarding application in AXA
When i inject the snippet into the source file of the webpage and refresh the page the browser throws some errors like "insecure content"
and there is no data in axa console.
can you please guide me is the snippet getting blocked?
Thanks