-
Notifications
You must be signed in to change notification settings - Fork 516
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
Graph API resolving to IPV6 sometime. #74
Comments
Resolving to IPV6 is completely acceptable. If your server is IPV6 capable, then this behavior is actually beneficial. We will not provide methods to force IPV4 in the SDK unfortunately. |
Lots of data centres in India are not IPV6 capable yet, we have recently faced this issue. May be you can mention this in the documentation. |
Could you configure your servers to not use IPV6 in that case? It shouldn't resolve to IPV6 if you aren't IPV6 capable, so it sounds like a misconfiguration. |
Can you tell me where exactly to put the code: |
Hi Rohit, Or you can simply grep for curl_init. Thanks, |
Graph API requests are resolving to IPV6 some times.
We can force the API to resolve to IPV4 by adding following code snippet after curl_init
curl_setopt($this->handle, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4);
The text was updated successfully, but these errors were encountered: