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
Hi. If I send a URL, for example, https://google.com/, as a string via the SendMessage API endpoint, I experience a 7-second delay before the curl command completes. The same issue occurs when using Swagger. It seems like it's trying to resolve the domain via DNS. However, DNS resolution works everywhere else, both in Docker and on the host machine, so it doesn’t appear to be a DNS problem. Has anyone else encountered this issue?
The text was updated successfully, but these errors were encountered:
Martin22
changed the title
Slow Response Time When Sending URL via SendMessage API
Slow response time when sending URL via SendMessage API
Oct 8, 2024
I figured out why there is a delay. The application on the phone must be running, through which the page previews are likely being fetched. If it's not running, it seems to wait for some kind of timeout, and the preview of the sent page won't load. It looks like a feature of WhatsApp, which probably can't be changed, but maybe the timeout could be shortened somehow?
Hi. If I send a URL, for example, https://google.com/, as a string via the SendMessage API endpoint, I experience a 7-second delay before the curl command completes. The same issue occurs when using Swagger. It seems like it's trying to resolve the domain via DNS. However, DNS resolution works everywhere else, both in Docker and on the host machine, so it doesn’t appear to be a DNS problem. Has anyone else encountered this issue?
The text was updated successfully, but these errors were encountered: