Chrome AutoFill not working locally - google-chrome

I am building a site that supports autofill and I need to test some edge conditions locally.
Chrome happily offers to store the credentials on our deployed version but it will not ask locally. I have tried to serve the site locally over HTTPS and served it under a different hostname than localhost with no luck.
Anyone know the details/restrictions on autocomplete in Chrome?
Thanks.

Related

Windows authentication not working properly on Chrome

So this is kind of odd.
My scenario:
Web server running IIS, hosting asp.net applications
SQL server
As they are on separate servers, I had to set up kerberos delegation. I have got this working.
So a user goes to asp.net application hosted on the web server, and it authenticates them to the SQL server.
On one of my web apps, when they go to it in Chrome, I get the error page with SQL authentication failed due to Anonymous user. If they go to the same app in IE, it works correctly.
Here is the really odd part - if they then go to it again in Chrome, it works!
So I guess there is some inconsistency in how Chrome authenticates.
I found someone suggesting it might be to do with the IIS negotiation providers, but as it needs kerberos delegation I have to have "Negotiate" as the first option or it fails completely.
I guess I could just tell users they have to use IE, but I would prefer to get it to work in Chrome.
Any thoughts?
(Possibly similar to Kerberos not working with Chrome but it's all on intranet zone, so don't think there's anything to whitelist)

Websites doesn't work within android google chrome browser

My problem is that I can't surf websites on the server I manage from within the Android Google Chrome browser.
All the websites on the server give me an error:
this site can't be reached
ERR_CONNECTION_RESET
but if I try a different browser other than chrome, it works.
The server has WHM/Cpanel installed and is running Apache 2.4. The websites are on hosted on cloudflare and consist of private PHP programming scripts.
What could be the reason of the this problem?

local / vpn pages via Chrome browser

If I'm looking for a local/intranet address while connect to a VPN, it works in safari or firefox but many times it will not work via google chrome
example address:
http://help/userui/ticket?ID=14273
Google Chrome takes me to a verizon page like so: "http://searchassist.verizon.com/main?ParticipantID=euekiz39ksg8nwp7iqj2fp5wzfwi5q76&FailedURI=http%3A%2F%2Fhelp%2Fuserui%2Fticket%3FID%3D14273&FailureMode=1&Implementation=&AddInType=4&Version=pywr1.0&ClientLocation=us"
How can I get chrome to realize that I'm looking for a page on an intranet on not to the public web?
Notes:
Using Cisco AnyConnect as VPN client
Chrome version 48.0.2564.97 (64-bit)
OSX 10.11.3
The best solution I've found on OSX so far is to use Safari which is better about detecting VPN pages.
Soon after you've navigated the pages Chrome starts to work as well. This must either be a DNS or caching issue, possible both (I'm no IT master).

Geolocation not working on Chrome even from a host server

I was working on a html5 file which uses geolocation. It was working fine in Chrome version 38.0.2125.111m from both loading the file locally and from a host server. Now, Chrome does not work for geolocation from either resource. I understand the security issue when running the file locally, but it still happens from any website that is running geolocation. I get the error message of "geocode service failed". BUT runs fine from both resources using Firefox. I have a windows 7 x64 laptop. The code that I am using is right off of Google geolocation example...
I've also went to the chrome's privacy-security-location settings and checked to use allow all sites to check location and still the problem continues... Help!
I think I found a clue. I copied the geolocaton file to another website and ran fine using the same chrome version which makes me believe that it is the google api keys that was causing the problem. I deleted the keys for both local and web host and will see in a few days if indeed this was the case. If it is, then I suggest not to establish api keys during development until app is ready for production.

FireBug in Chrome doesn't show up on local websites

When I right-click on the local html page and select "Inspect with FireBug Lite" nothing happens... on regular online sites it works except for "https://chrome.google.com/webstore/category/apps"
anyone had the same experience? I have the latest version of the extension (but it's from 2011 :/)
UPDATE: on some local sites it does show! on two web apps (PHP, Rails) it did work, but on a few static HTML files I tried it didn't....
Apparently this is normal...:
It doesn't work on local pages
If by "local pages" you mean files accessed via "file:///" protocol then yes, Firebug Lite doesn't work with "file:///" protocol. This is a JavaScript security restriction to prevent malicious web pages from accessing files in your your machine. Also, please note that the while you can load a "local page" in the browser (it will render properly) it will NOT behave exactly the same as when hosted in a web server.
Solution:
You can solve this problem by loading your page in a web server installed in your machine, so you can access that local files through "http://" addresses. This is the best solution: it is safer, and you'll get the most of what Firebug Lite can give you. I recommend using Apache HTTP Server, but you can use anyone (like IIS for example).
Which exact URL are you visiting? It is an internal Chrome's page
(like "chrome://downloads/"), or some page related to Google Chrome
extensions "https://chrome.google.com/extensions/")?
Google Chrome won't allow content scripts (required by Firebug Lite)
running on such pages. The problem is that Chrome does not inform the
user and neither the extension about it. In other words, there is no way
to Firebug Lite know if the content script was loaded or not, and we
worked around this by sniffing the URL and detecting when you visit
URLs that begins with "chrome://" or "https://chrome.google.com/extensions/",
alerting users in such cases.
You've few options to fix the solution.
One is to use Mozilla Firefox.
Second, install a web server on your system. Try WAMP or XAMPP. Once installed, store all the web pages in the root folder of the web server you just created. Save all the web pages and html files in C:\xampp\htdocs. Navigate to the locally stored webpages using your web browser by going to “127.0.0.1/index.html” or “localhost/index.html”.
Now you can use Firebug-Lite for Google Chrome on local files.