Fix for case of weird devices sending weird things #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Situation:
Local network has pfSense router with upnp enabled, also has Ubiquity Cloudkey 2.0 that feels like putting its oar in.
A reply comes in to the discovery from the cloud key:
This results in:
java.io.FileNotFoundException: http://10.3.0.75:8080/upnp
(Apparently the URL they provide results in a 404)
After this, the proper router reply comes in. This change is to basically ignore any device where we get errors trying to parse or understand them.