-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jaxws uses ip, instead of DNS #21
Comments
Unfortunately I dind't wrote this module, I just ported the original version under a more maintainable maven project. |
Funny, I just solved it. I tried it before, but intellij did not seem to pick up my code changes. The library uses the xaddr the server gives it, so that being the XAddr. However this is the actual ip address of the service, and not however you reach it. I solved it by doing this: In OnvifDevice init, this code needs to be replaced, more specifically (for each service):
I'll look into making a pr and uploading it. |
That would be great! |
Hi,
I am using this library, to try and connect to cameras, that are behind reverse proxies. However it seems somewhere in the code it changes the camera.localhost to the effective ip address (as in the ip of the camera, not how you connect to it), and that ip is unreachable. So the eg, I use the host https://camera.localhost, and I create an OnvifDevice, but it fails whenever I try and use a service, like media or ptz, since it somehow resolves to a.b.c.d/onvif/media_service, but this I cannot reach (reverse proxy).
Is there a way to trigger all services of Onvif device to keep using the dns instead of the ip of the interface where the camera runs?
The text was updated successfully, but these errors were encountered: