You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are running into an issue with this library. We have created a application that uses this library. Sometimes when we run the application it works as expected, but sometimes an exception is thrown with this message:
Error resolving address
If it doesn't work, it never resolves itself unless the application is restarted (and when it starts back up its a coin toss if it works or not). Looking over the code it seems this message comes from the cpprest/Casablanca library here but we have not been able to find out anything past that on the library end.
Things we have tested:
Tested with (libazure: 5.0.0, cpprest: 2.8) and (libazure: 6.0.0, cpprest: 2.10.13) on Ubuntu 16.04
Time is set right
Doing a packet capture shows that when it doesn't work there are no packets being sent (as determined by tcpdump)
We can connect to the internet and dig returns a response for the address being requested
Running with a debug build doesn't give us any more information. Is there something else we can do? Any ideas to try?
The text was updated successfully, but these errors were encountered:
From the error message, seems it's because the request cannot successfully connect to the server endpoint.
Could you share the protocol you were using (HTTP or HTTPS), and whether there's any proxy when you met this issue?
We are running into an issue with this library. We have created a application that uses this library. Sometimes when we run the application it works as expected, but sometimes an exception is thrown with this message:
Error resolving address
If it doesn't work, it never resolves itself unless the application is restarted (and when it starts back up its a coin toss if it works or not). Looking over the code it seems this message comes from the cpprest/Casablanca library here but we have not been able to find out anything past that on the library end.
Things we have tested:
tcpdump
)dig
returns a response for the address being requestedRunning with a debug build doesn't give us any more information. Is there something else we can do? Any ideas to try?
The text was updated successfully, but these errors were encountered: