I've recently been asked to help support a system which uses the PHP Proxy provided by SWFJunkie. In following the proxy's install steps I get to Step 4 at which point I get no results. I've tried hosting on Apache and IIS, have confirmed that URL rewrites work correctly on both platforms and that CURL is correctly installed, and have ensured there are no firewalls blocking my requests.
In researching this issue I've seen that Twitter have been changing their API rules (with more changes set to take place in March next year). The last activity I can see on the Proxy project was back in 2010, after which it seems to have gone dead. Before I put in more effort trying to get this to work I thought I'd ask - is anyone else currently using this / do you have it working?
If you have it working I'd welcome any tips / advice you have also, but mainly I just want to know in advance whether this utility still works in order to justify spending time on it.
Thanks in advance.
the proxy does still work, but I had to tweak the code a little.
Thanks to #MikeHayes for the solution: Twitter OAUTH - returns response code of "0"
For anyone else having this issue, the quick fix is to update Tweetr.php. Find the code matching what's below & insert the additional (commented) line on the end.
$opt[CURLOPT_URL] = $twitterURL;
$opt[CURLOPT_USERAGENT] = $this->userAgent;
$opt[CURLOPT_RETURNTRANSFER] = true;
$opt[CURLOPT_TIMEOUT] = 60;
//BEGIN UPDATED CODE
$opt[CURLOPT_SSL_VERIFYPEER] = false;
//END UPDATED CODE
Thanks again to Mike & good luck to anyone else currently having this issue.
Related
This issue has taken up all my day, and I can't figure out whats going on
I can see that my service worker is registered , however "sometimes" when I click offline in developer tools the ServiceWorker for my domain just disappears!!
But this is the main problem when I reload the app I see the following behaviour.
You can see the ngsw.json is loaded twice and the main.js is loaded 3 times! main.d3ae2084xxxx && main.bbe5073dxxxx && then main.d3ae2084xxxx again!
If I inspect the response of both ngsw.json requests you can see that both show main.d3ae2084xxxx as the correct version of main.js but it still loads main.bbe5073dxxxx...
First ngsw.json request
Second ngsw.json request
Whats even more frustrating is the actual loaded version is the previous main.bbe5073dxxxx...!!!!
If anyone has any ideas how this can be happening please let me know.
Update... So found out about this excellent little endpoint
https://you-app-url/ngsw/state
This will give you lots of debug information about your service worker.
In my case this
Driver state: EXISTING_CLIENTS_ONLY (Degraded due to failed
initialization: Hash mismatch (cacheBustedFetchFromNetwork):
https://dev-xxxx.net/main.eb8468bb3ed28f02d7c2.js: expected
b5601102b721e0cf777691d327dc965d40d1c96e, got
83c18fdb4a5942c964a31c119a57e0b8e16fe46e (after cache busting)
So looks like this is going to be a CDN issue of some sort in my case, will update with an answer when I know for sure.
You've probably resolved this by now, but I had the same issue which turned out to be due to the CDN (Cloudflare in my instance) was optimising the content.
In Cloudflare the key option is 'Auto minify' that needs to be disabled.
According to the OpenShift docs, the following should return a result:
curl -X GET https://openshift.redhat.com/broker/rest/api
However, any call to the API actually just returns a single whitespace - including those called with username & password.
I've confirmed the issue from several different machines accross the globe.
What might be the reason?
Inspired by a similar question regarding Twitter, I added .json at the end of the URL and it worked:
curl -X GET https://openshift.redhat.com/broker/rest/api.json
It's kind of disappointing that RedHat never replied to any inquiry regarding this issue.
The issue is logged here: https://bugzilla.redhat.com/show_bug.cgi?id=1324208
You can add yourself to the "cc" if you would like to be notified as the fix gets rolled out to production.
FYI, asking for help on a public forum and giving it only 4 hours for a response from the company seems a bit much. In the future it may be worth it for you to either check for open bugs, or to ask the company directly instead.
I am using Google Document AclFeed APi to get the list of users to whom the document is shared. This is the code I am using
AclFeed aclFeed = docsService.getFeed(new URL("https://docs.google.com/feeds/default/private/full/file%3A"+fileId+"/acl"), AclFeed.class);//No I18N
Until last week everything was working fine , but from past two days I am getting the SocketTimeOutException for many requests...Is anyone else facing this issue? Any help will be grateful..
TIA,
VijayRaj
It happens a lot. What is your timeout set to? As an example the default on AppEngine is 5s which is way to low.
I'm using this example to test geolocation API http://www.w3schools.com/html/tryit.asp?filename=tryhtml5_geolocation_error
But, I always get Location information is unavailable. message. I tested it on different browsers, same problem. I have geolocation enabled in browser.
Also, I tried uploading this to a local server (XAMPP), but problem remains (same error code).
What am I doing wrong here, its taking me hours now?...I appreciate any help on this, thank you.
EDIT: When I try to locate myself using this service http://www.hostip.info/index.html its giving me error message ... actually we haven't a clue.. When I type in some random IP address, works perfect. Whats going on here?
Has anyone tried accessing bungie.net reach stats api (statistics from Halo Matchmaking)?
As described here http://www.bungie.net/fanclub/statsapi/Group/Resources/Article.aspx?cid=545064
I can't seem to get any data returned, for example if i use this (with correct API key and gamertag values of course) ignore the first 2 asterisks ...
**http://www.bungie.net/api/reach/reachapijson.svc/player/details/byplaylist/MyIdentifierAPIkey/Gamertag
I don't receive a response - but no errors either, am i doing something wrong?
looking to use this for a Titanium (appcelerator) app eventually.
Any help or advice welcome, thanks in advance.
Unfortunately the API is not yet live to the public. I asked in a Private Message. They didn't say when it would be live.
In the Docs that Achronos posted, he put spaces in the URL's, I'm not sure if those are supposed to be there or not, so I tried it with the spaces and I got a 403 Forbidden error page. When I remove all the spaces, I get an error page that says:
Request Error
The server encountered an error processing the request. See server logs for more details.
I kinda can't check the server logs though... Bungie did say they were having some issues with the site though, so this might be a biproduct of that. I want them to get it working soon though, I wanna see just what it can do!