I am developing a personal productive app. The bookmark manager is part of it.
I use a lot of two-step verification websites so it is difficult to bypass that to get the webpage favicon.
However, when I use "chrome://favicon/https://stackoverflow.com/" I can easily get the favicon of any website.
But the issue is that it works when I open in a new tab but they don't work on my webpage however, in the
For example.
<img src="chrome://favicon/https://stackoverflow.com/" />
Any suggestions on how to fix it. Thanks a mill in advance.
You can Get favicon by https://stackoverflow.com/favicon.ico Of any website. Just add /favicon.ico at the domain. There is no need of using chrome://favicon
Often you can get icon of site by requesting <website>/favicon.ico. For example, it works perfectly for https://stackoverflow.com/favicon.ico. (and it is 32x32, not 16x16 using chrome://favicon).
I am trying to add a simple link to text in google site.
For some unknown reason, it doesn't seem to be working.
<p>my link</p>
When I click on it I see the error:
The requested URL /embeds/16cb204cf3a9d4d223a0a3fd8b0eec5d/www.google.com was not found on this server. That’s all we know
Any idea what is causing this error? I am aware I can just use google's insert link graphical interface, but I am trying to understand why is coding not working.
Your code is is bit incorrect, have you tried out this.
<p>My url
i wrote a little extension to my site.
I've added my site in Webmaster Tools in purpose of verified, which is www.love2live.pl.
I've a button on my site Add to chrome, when i click in, then i got a message like:
inline install failed: Installs can only be initiated by one of the Chrome Web Store item's verified sites.
My extension is a private, but people with link may find it, i dont't know what i should to do yet, that will be working fine.
In <head> i added:
<link rel="chrome-webstore-item" href="https://chrome.google.com/webstore/detail/myID" >
and in button i added:
<button onclick="chrome.webstore.install(undefined, undefined, function(err) {console.log('inline install failed: ' + err)})" id="install-button">Add to Chrome</button>
Any solutions?
Regards,
Adrian
You may refer with this thread. There might be an issue with https verified sites. Try to switch the verified domain to not be SSL and see if it works. Also according to this documentation, inline installations can only be initiated by a page on a site that is verified (via Webmaster Tools) as being associated with that item in the Chrome Web Store for security reasons. You may double check your configuration.
I mean the html code generated when you get into ftp://yourserver... I tried to google it with no luck, not found in the project webpage either. I'd like to modify that code to do it more mobile friendly.
Thank you in advance
If you use a browser to load an FTP directory then the HTML page will be generated by the browser from the directory listing.
For example, see this part of the source code for Google Chrome.
When I go to our web site through HTTPS mode, Chome is reporting an error saying that the page contains secure and not secure items. However, I used Firebug, Fiddler, and HttpDebuggerPro, all which are telling me that everything is going through HTTPS. Is this a bug in Chrome?
Sorry but I'm unable to give out the actual URL.
A bit late to the party here but I've been having issues recently and once I had found a http resource and changed it was still getting the red padlock symbol. When I closed the tab and opened a new one it changed to a green padlock so I guess Chrome caches this information for the lifetime of the tab
Current versions of Chrome will show the mixed content's URL in the error console. Hit CTRL+Shift+J and you'll see text like:
"The page at https://www.fiddler2.com/test/securepageinsecureimage.htm contains insecure content from http://www.fiddler2.com/Eric/images/me.jpg."
I was having the same issue: Chromium showing the non-secure static files, but when everything was http://.
Just closing the current tab and re-opening the page in another new tab worked, so I think this is a Chromium/Chrome bug.
Cheers,
Diogo
Using Chrome, if you open up the Developer Tools (View > Developer > Developer Tools) and bring up the Console and choose to filter to warnings, you'll see a list of offending URLs.
You'll see something like the following if you do have insecure content
The page at https://mysite/ displayed insecure content from http://insecureurl.
For the best experience in finding the culprit, you'll want to start your investigation in a new tab.
It is possible that a non-secure URL is referenced but not accessed (e.g. the codebase for a Flash <object>).
I ran into this problem when Jquery was being executing a a few seconds after page load which added a class containing a non-secure image background. Chrome must continually to check for any non-secure resources to be loaded.
See the code example below. If you had code like this, the green padlock is shown in Chrome for about 5 seconds until the deferred class is applied to the div.
setTimeout(function() {
$("#some-div").addClass("deferred")
}, 5000);
.deferred
{
background: url(http://not-secure.com/not-secure.jpg"
}
Check the source of the page for any external objects (scripts, stylesheets, images, objects) linked using http://... rather than https://... or a relative path. Change the links to use relative paths, or absolute paths without protocol, i.e. href="/path/to/file".
If all that if fine, it could be something included from Javascript. For example, the Google Analytics code uses document.write to add a new script to the page, but it has code to check for HTTPS in case the calling page is secure:
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
On the release of Chrome version 53 on Windows, Google has changed the trust indications to initiate the circle-i. Afterward, Google has announced a new warning message will be issued when a website is not using HTTPS.
From 2017 January Start, Popular web browser Chrome will begin
labeling HTTP sites as “Not Secure” [Which transmit passwords / ask
for credit card details]
If all your resources are indeed secure, then it is a bug. http://code.google.com/p/chromium/issues/detail?id=72015 . Luckily it was fixed.