2013-05-07, 17:29:58
i tried "$nocurl = true;" adn got his result:
get_api_details: plugin i18n_base.php
get_api_details: http://get-simple.info/api/extend/?file=i18n_base.php
cache check for http://get-simple.info/api/extend/?file=i18n_base.php a530edfa8073b06f07218c5b4a0472d6.txt
API via fsock
Duration: 0.10256
get_api_details: plugin i18n_navigation.php
get_api_details: http://get-simple.info/api/extend/?file=i18n_navigation.php
cache check for http://get-simple.info/api/extend/?file=i18n_navigation.php 242db151f05a3e80879be205a51fa831.txt
API via fsock
Duration: 0.10099
get_api_details: core
get_api_details: http://get-simple.info/api/start/v3.php?v=3.2.0
cache check for http://get-simple.info/api/start/v3.php?v=3.2.0 1b904d26e4e8c9e2dde21d9411314f59.txt
API via fsock
Duration: 0.10093
These times look more realistic, just a bit more than 100ms.
But, if there's no bug in the code, it doesn't get any data as well.
So in the end both methods don't work.
Looks like cURL is failing before timeout actually happens and returns the wrong error code.
I'll test a bit more and ask my hoster about this.
Strange thing, it's one of the biggest hosters in Germany, cannot imagine such a problem happening unrecognised.
p.s. don't get confused by the different plugins in this debug report - i did a test installation on my hoster to be able to try things without disturbing the actual website.
get_api_details: plugin i18n_base.php
get_api_details: http://get-simple.info/api/extend/?file=i18n_base.php
cache check for http://get-simple.info/api/extend/?file=i18n_base.php a530edfa8073b06f07218c5b4a0472d6.txt
API via fsock
Duration: 0.10256
get_api_details: plugin i18n_navigation.php
get_api_details: http://get-simple.info/api/extend/?file=i18n_navigation.php
cache check for http://get-simple.info/api/extend/?file=i18n_navigation.php 242db151f05a3e80879be205a51fa831.txt
API via fsock
Duration: 0.10099
get_api_details: core
get_api_details: http://get-simple.info/api/start/v3.php?v=3.2.0
cache check for http://get-simple.info/api/start/v3.php?v=3.2.0 1b904d26e4e8c9e2dde21d9411314f59.txt
API via fsock
Duration: 0.10093
These times look more realistic, just a bit more than 100ms.
But, if there's no bug in the code, it doesn't get any data as well.
So in the end both methods don't work.
Looks like cURL is failing before timeout actually happens and returns the wrong error code.
I'll test a bit more and ask my hoster about this.
Strange thing, it's one of the biggest hosters in Germany, cannot imagine such a problem happening unrecognised.
p.s. don't get confused by the different plugins in this debug report - i did a test installation on my hoster to be able to try things without disturbing the actual website.