For testing my Google Places key, I ran a simple web address in chrome: http://maps.googleapis.com/maps/api/place/nearbysearch/json?location=50.6483,70.129&radius=2&types=train_station&key=myKey
The result was:
{
"debug_info" : [],
"html_attributions" : [],
"results" : [],
"status" : "REQUEST_DENIED"
}
I generated another key from API console, but that also didnt work. I have enabled Google Places in Servies tab of API Console. I checked other questions. This is a common question. Is there any solution yet? I have been using the same key 4-5 months back. It was working. The same link worked 4-5 months back, but now the link is not working, even tried with many different keys
This kind of issue is probably best handled by raising on our issue tracker: https://code.google.com/p/gmaps-api-issues/
Related
I'm going crazy searching for this event but I didn't find a single solution for that.
That's the situation :
Wordpress in a Azure Windows App Service.
All works fine, but in the eventLog.xml a see every day, seems scheduled, a log like that :
A potentially dangerous Request.Path value was detected from the client (:).
at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)
The page request is like that :
https://www.mywebsite.com/my-category/my-article/https:/www.mywebsite.com/my-page/
I'm sure that those links are not in the google serp and there is no link to those pages.
I found that :
Azure websites throw 500 error when there is a colon in the URL
It's the same error, but I can't afford the same solution.
It seems to be related to the IIS Request Filtering feature, but I'm not a Windows wizard and I don't know how to disable this feature on Azure.
Can anyone solve this issue?
IIS VERSION : 10
How can I get an Google Translation API key to connect Trados Studio to Google Translation API?
In this instruction of SDL below, the key seems to have been available in the list in "APIs & services > Credentials" of Google Cloud console.
https://urldefense.proofpoint.com/v2/url?u=https-3A__gateway.sdl.com_apex_communityknowledge-3FarticleName-3D000005906&d=DwICaQ&c=Fge86U5Za1d7PUAcaTHoag0MToOH_fWpqWSEoP8Euxo&r=xdz4rRCzUCiMTlPzdnPEy9-9jLzZpm5SDgO1bwvO1T0&m=qS3KpcI4kSqBPB9p5G3IWLP2u9lzbF5ZeA6cdFqdAJY&s=lEyhu-1AVxnMDNj247L28iKqLLfpSCLyAzAOLhjf8lM&e=
But now, the "Key" column does not exist in the list. Instead, I got a Jason file following the steps in the console. But any values in the fields in the file like "project_id", "private_key_id", "private_key", and "client_id" all didn't work. I get an error "The API Key you have entered cannot be validated with Google".
I could make the key following the steps described in this page.
https://cloud.google.com/docs/authentication/api-keys#creating_an_api_key
The steps looked almost the same as those in SLD's instruction page.
But somehow, this link below in SDL's instruction page didn't work correctly for me.
https://console.developers.google.com/cloud-resource-manager
I got this error when I tried from the link.
I'm trying to use the google api for auto-complete.
I created a key and did some testing, due to an error in my code, that sent many requests in a short time I had the error: OVER_QUERY_LIMIT
I made the correction of my code, deleted the used key and created a new one. Now I get the following message:
{
"error_message" : "The provided API key is expired.",
"predictions" : [],
"status" : "REQUEST_DENIED"
}
Does anyone have any idea how to solve it?
The Message you are getting seems to be very clear.
You could have a licence an this license seems to be exceeded.
Please read the documentation.
The clarity of the message is quite obvious.
The problem is that google warns you that you have a 100k limit available.
The detail is in: these 100k is only available when billing is activated, without activating billing the limit drops to 1.
I would never imagine that.
But it's settled!
The tip is for anyone to go through the same problem
we have an integrated with google picker(read-only scope,Docs view) it use to work fine but recently some users are getting blank screens as soon as the pop up shows but when they select some filter everything starts working fine after that no problems.
using developer tools i see all apis returning 200 for that first request
but there were no docs in response(i believe this is the api responsible for bringing docs in picker 'https://docs.google.com/picker/pvr')
when there are no docs returned in above api google is calling another api i assume it is to log error's probably(//docs.google.com/picker/ohnoes)
this api has following error params in it
&error=Cached and requested query mismatch
&line=Not available
&viewToken=["all",null,{"query":null}]
&ms=97
&transferDocs=false
&numErrors=1
has anybody else faced the similar problem
what do error "Cached and requested query mismatch" means in context of drive docs
Fyi - most accounts facing this problem seems like are of company domain for ex "jondoe#company.org"(this is a google account with company domain)
Filters Image
Thanks for your help.
not sure but looks like issue was may be related to google bug
https://issuetracker.google.com/issues/64825685
for me the code that was not working was:
addView(google.picker.ViewId.DOCS)
replaced this code with below code which works as expected
var view = new google.picker.DocsView();
view.setIncludeFolders(true).setOwnedByMe(true).setParent('root');
addView(view).
I've added my code to pastebin at the following address:
http://pastebin.com/L03zGPhS
The service is up and running.
I can invoke it. I am additionally using firebug and getting the following results on the POST:
POST http://localhost:51204/AddrService.asmx/GetZipCode
15ms
HeadersPostResponse
JSON
zip
"40"
Source
{'zip': '40' }
Showing the service function:
[WebMethod]
public List<Zip> GetZipCode(string zip)
I can get this to work with jQuery 1.4.2, but I'm upgrading a lot of jQuery widgets to 1.8 and can't get the autocomplete to work. Am I missing something they changed in the AJAX autocomplete call. Documentation to a correct answer will suffice if it is useful.
UPDATE I found through Google Chrome that I'm getting a 500 error. I'm not certain why because I'm hitting localhost on both the service and the aspx page. Does anybody know if they changed something that would affect the security of hitting localhost, or if I could have possibly left out and important jQuery reference that would let autocomplete work for 1.4 but not 1.8?
Maybe this sheds light on your problem — the autocomplete API states that :
"You must always call the response callback even if you encounter an
error. This ensures that the widget always has the correct state."
(source : http://api.jqueryui.com/autocomplete/#option-source)