"Our Google's MAP implementation was working fine when suddenly an alert was being prompt by Google informing to any visitor that Google's MAP was deactivated in our site because it didn't have the correct domain references or because the key was wrong; the same key was working fine in one of our sub-domains, which we use for development purposes, so we were pretty sure that the issue didn't rely on our end. We also double checked the settings on Google's developers console and everything is setup properly.
At the end we removed the key from the API call temporarily until we find a solution; what are the consequences of not including the key and what recommendations could you give us to solve this issue?
We are also using Google's Page Speed technology.
One thing I tried was to make sure that the Referer patterns shown in the Google Developers Console were sufficiently generalised, e.g. *.mysite.com/* rather than mysite.com
This apparently helped but further testing was inconsistent with the alert shown almost always on Windows Safari (5.1.7) and Firefox (29.0.1). In contrast, it was rarely shown on Safari on iOS.
As my web app is unlikely to make 20000 requests a month, I decided to ditch the key and use
<script src="http://maps.googleapis.com/maps/api/js?sensor=false"></script>
So far, this has worked without any apparent issues.
Related
I was asked to implement the Google Tag Manager scripts into the React application. I've added the scripts to head and body of my html file. I've tested the site in the Preview mode of GTM and everything seems to working fine. Clicks and route changes are tracked correctly.
I have one doubt... What about the localhost development ? Is it going to generate unnecessary logs on the analytics (which I have no access to)? Or maybe it's just enough to paste the snippets and that's it?
I can't find an answer so that's why I decided to ask here.
If someone has some experience on that topic - please let me know :)
I would advise you to map separate Google Analytics property IDs by either a datalayer variable, URL or custom JavaScript to return a separate property ID based on whether users are accessing your website from either your localhost development environment, your UAT environment (if any) and then your production environment (or others as applicable).
Essentially you're looking at having something that says "if the URL contains "localhost", return my development property ID", then use this variable name in your Google Analytics tag(s) instead of a static value.
Yes, unfortunately all your existing testing is all in your profile because if you had the production property ID configured and fired off a bunch of events and pageviews, it absolutely collected and sent there as part of the debugging experience. Generally though, that's a low concern on a production app because you make up such a small portion of overall traffic; you're just a couple of blips in the larger dataset.
The title pretty much says it all. When I'm running HTTP(S) Test Script Recorder, one particular page becomes unresponsive - when I click on something it just reloads. The recorder itself is working fine, it is recording every step. And the problem is not proxy related. I've successfully recorded other pages of the same website. When I'm not recording, there are no problems.
It's a .NET 3.5 project.
The page itself has a lot of forms, file uploads, etc, but as far as I know, it should not interfere with recording or even more - with browsing the page. When debugging the project, no breakpoints are hit, so I assume that something gets lost before reaching the server.
Browsers that I've tried: tried FF, Chrome, Edge, IE.
Tried recording the web locally and online. Same thing.
Played around (reinstalled and whatnot) with certificates, didn't help.
Has anyone encountered such a problem? What could be done to fix this? I'm more interested in finding the solution, than a way around (blazemeter, badboy). Any help would be very appreciated.
EDIT: I tried recording with blazemeter and it worked. But when looking at view results tree I noticed that the request path and parameters don't change, even when in the HTTP Request Sampler they are different. So there's no solution yet
This often happens to me and what I've found is that JMeter changes the root certificate in the bin folder every week. So usually the HTTP traffic is fine but certain HTTPS traffic won't work. So make sure that your browsers are seeing the latest JMeter certificate and not using an old one that doesn't exist anymore. On Windows, Chrome and IE use the certificates in Internet Options, while Firefox needs to have it added to it manually.
It turns out that in Test Script Recorder HTTP Sampler Settings choosing Type: Java was all that was needed. I suspect that the issue was related to file upload being involved.
Our customer experienced multiple errors on a demonstration to a customer of theirs.
The site is asp.net 3.5 based and has been running pretty well lately. They said 2 hours later site was ok again... (needless to say they are not happy)
The traces in the health log look very weird, it appeared to be as if incomplete pages were returning to the server for processing..
A fair of of the errors were errors generated by scriptresource.axd with bits of the page source showing up as part of the url... very very odd. I'd never seen this before...
I was talking to their lead tester who then told me this only happened during a webex (cisco sharing product) demo and was fine after...
Is it possible the webex session could have impacted the site http stream between client and server...
This is a known IE8 issue. I bet you will see Trident/4.0 for all "broken" requests in the user agent field. (Google for "IE8 4K bug")
You can either run a different browser or appply the latest IE8 patch (this issue has already been fixed)
I posted a question the other day about why IE8 would not allow me to embed a page using the OBJECT tag. Per that discussion, and per my other research, I decided to just go with an IFRAME as it was not clear that the third-party application actually needed to be in an OBJECT.
Now here I am, a day later, finding out that IE8 has the same cross domain issue with IFRAME that it does with OBJECT. Is there any way around this? Why can I not find any discussion about this being an issue?
It has been awhile since I have had ot use an IFRAME for anything but I am pretty certain that this used to be really easy to do. Am I missing something, or am I really stuck going back to early AJAX days of having to build a local PHP proxy script to proxy my request to the remote server?
Take a look at EasyXDM. It's a library which wraps cross-browser quirks and provides an easy-to-use API for communicating in client script between different domains using the best available mechanism for that browser. Caveat: you need to have control over both domains in order to make it work (where "control" means you can place static files on both of them).
I want to use Google Analytics on my Vkontakte application (written with Flex). Vkontakte does not support naturally in Google Analytics (not as Facebook) which means I can't even put the Google Analytics JS at the bottom of the page (or even use JS for that matter). What I can use is the AS3 library of Google Analytics, but for some reason it reports of failed gif requests every time I use it to report on an event.
Is it even possible to use Google Analytics on the described environment?
If so, what could be the reason of the failed gif requests? Is it debugable?
Update #1:
After debugging the "Google Analytics for flex" source code, I got this error: Error #2035: URL Not Found.
Update #2:
It turns out to be a known bug as suggested here. It works perfectly on IE.
Update #3:
It works on FF when I disable the "ABP Tracking Filter (by rick752)" filter at the "AdBlock Plus" extension.
It's possible, the problems I've experienced were due to FF problem as stated in the question.
One potentially relevant way to debug this: install a network monitor like Fiddler, and look at the requests going over the wire. Do you see the right GIF get downloaded? If so, you're good. If not, you'll see what's going on on the network.
Here's some info from Google on debugging the gif requests. What do you mean when you say it failed?