I have a website which has an SSL certificate installed. If I navigate to the site via https://www.[MY-SITE].com then it flashes up in Chrome for a second with a green https:// indication. Then it greys out and shows the message that the site is loading up insecure content.
Some of the links on the site are still the old http:// versions but it isn't actually loading anything from the files it is linking to. One thing I thought of was that I don't have access to change the Google Analytics code to the https:// so it is still on the http:// in the admin settings on Google. Would this be the issue?
Thanks,
Jack
It may occur mistakes I think. I just search out some post from web regarding your queries.
please read this link :
http://blogoscoped.com/archive/2007-12-13-n83.html
http://code.google.com/p/r-google-analytics/issues/detail?id=1
I hope it will be helpful for you.
Related
HTTPS has been enabled on a site and the Google Search Appliance now isn't able to crawl or access the site. My tech team can't figure out what is the issue and I haven't been able to find a definitive solution. Any help you can provide would be appreciated. Thx.
You should receive an error when using Real-time diagnostics but the best way, I've seen, is to use the "Forms Authentication" setup page.
Configure the sample URL to point to your site's home page and set the pattern to be the root URL for your site.
When you click "create" an SSL link will try to be created and you'll likely receive an error back at this point.
My guess is that the certificate on the web site may not be 'perfect' (the GSA is less forgiving than browsers are).
I tried using Google Webmaster tools to re-crawl the site and it hasn't helped.
Does anyone know why the link on Google might say 'halalgems.com', but redirect to another site?
The description is also incorrect.
Unfortunately, it appears as though your website has been hacked, and not a problem with Google.
After looking at the response from your website once someone goes to it from that google page, it is your website that does the redirecting.
I cannot determine the source of this issue, as that would likely require access to your server. Good luck with tracking it down!
Okay, so I have my main site, www.mydomain.com.au along with my mobile site which is within a subdomain, m.mydomain.com.au.
I am trying to submit my subdomain to Google Webmaster Tools, although it cannot seem to verify it. I have tried with the HTML file upload and the meta tag option to.
I can verify that the Google HTML file is DEFINITELY uploaded since the link Google provides to check if it is there is working perfectly. Also, I have checked my source code and the meta tag is also definitely there.
My .htaccess file has a mobile redirect so I thought that may have been the problem, so I deleted that file to check if it would validate, but still no luck.
I have approximately 12 websites that are setup the EXACT same as this one, and all of their mobile sites/subdomains verified with Webmaster Tools perfectly.
This is my error message: We were unable to connect to your server.
Does anyone have any suggestions to why Google cannot verify my mobile site?
Google doesn't see sub domains...they see the folder where the sub domain is located. Delete the site and add is again as mydomain.com.au/m
Google will see it and add it to Webmaster tools...I just did this for my sub domain. That's how I worked it out...
You can verify them from here https://www.google.com/webmasters/verification/home?hl=en
It is wrong that google is not seeing sub domains. you can check it with site:yoururl. with your main domain you will get your sub domain as well.
This is just a quick question really for my own peace of mind more than anything.
When accessing an app hosted on Heroku through https://myapp.herokuapp.com I get a warning in Google Chrome and Firefox (but not Safari) along the lines of:
You have requested an encrypted page that contains some unencrypted information. Information that you see or enter on this page could easily be read by a third party.
I don't really want to pay the $20 a month for the SSL-Endpoint addon and was just wondering why these warnings appear and whether there was a way around it/how to find the content that is unencrypted.
I have tried both with and without config.force_ssl = true
Any suggestions? Any help would be appreciated
Turns out that this was an issue with a request from Google maps.
As far as I can remember, they changed their API to allow access over https:// after we began development.
It was simply a case of following the new process that was documented on the Google API page
I'm hoping this is just a bug on Facebook's end that will be fixed soon, but in my Facebook Connect app I'm launching the dialogue FB provides to make a post. This dialogue is launched on a page with an SSL connection. In this dialogue the profile pic for some users comes up with a security warning while others display correctly. I'm already setup to use Facebook's SSL javascript file instead of the HTTP file.
This is a bug at Facebook, but there's a work-around. When you use Facebook Connect to show a profile pic, you must set facebook-logo="false" on the fb:profile-pic FBML tag. (Note: the default is "true"). If you do this, and follow the instructions at facebook for using ssl, then the profile pic will be served using the correct protocol. If you leave it set to "true", then you always get the profile pics over http.
The bug is reported at http://bugs.developers.facebook.com/ as issue 5507 and possibly 7072 and 8485.
Also check whether you are serving the xd_receiver under ssl. The debugging hint at the bottom of this page can help you find if there are requests going to facebook other than the pictures which might not be SSL, thus confusing their determination of whether the page is under ssl: http://wiki.developers.facebook.com/index.php/Facebook_Connect_Via_SSL
I would use fiddler and see if there are other requests going to facebook which are not ssl, that will probably give you an indication of what is being missed, or if it is a bug.