I am getting 404 error while accessing Google Chrome - google-chrome

While trying to access my application in google chrome some urls are working fine and some are getting 404 error. My application is working fine in other browsers like IE , firefox ...etc. Please suggest me some information to allow my application working fine for all urls

You have to explore chrome settings for privacy and security, proxy settings etc.
chrome://settings/system. make your proxy settings as system settings instead of manual.

Related

Error with google adsense js on my computer

It seems like I have an issue with google adsense as the ads are not displaying on chrome nor firefox on my computer but they are displaying on opera when it's on vpn. I tried this with both wifi and mobile 3G data but I keep getting this error:
Failed to load resource: net::ERR_CONNECTION_REFUSED pagead2.googlesyndication.com/pagead/js/adsbygoogle.js:1
Note:
I previously had adblock on chrome but I uninstalled it long ago so it shouldn't be the reason
I removed and re-installed google chrome
I never used firefox before (so there's no adblock on it)
When I use 3G mobile data, the ads still don't show on my computer but do show on my phone (android google chrome)
I have this same error message on all websites I access even if it is not mine
I faced a similar kind of issue:
NET::ERR_CERT_AUTHORITY_INVALID
//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
Found that this was due to VPN blocking //pagead2.googlesyndication.com/pagead/js/adsbygoogle.js since it thinks we are accessing a site that is not authorized to be used
So regardless of AdBlock or without AdBlock, we will see the adblock message.
Not sure if you are facing same issue but it would be good to check your firewall/company vpn if any.

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)

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.

Google Chrome returning 503 Service Unavailable

I have been having an issue lately with Google Chrome. Some sites, seems to be completely random, are returning a 503 Service Unavailable error message. The last one I received was from my hosting provider when trying to access my CPanel. I can access the same URL completely fine in Firefox or IE. It seems to be isolated to Chrome.
I have tried the following:
Disabled all extensions
Logged in/out of my Google account
Cleared all cache and history
So far, nothing seems to correct the issue. It's becoming more and more aggravating from what was once a pretty reliable browser.
I am running:
Windows 7
Chrome Version 36.0.1985.143 m
I was hitting the same issue. Mostly, it would occur on intranet sites at work, but it happened with a few exterior sites. Loading in IE Tab would work fine.
I was able to solve the issue by upgrading to 64-bit Chrome. I'm not sure why that fixed it, but I think it had something to do with a conflict between Java and Chrome (It looks like I have both 64bit and 32bit Java installed side-by-side).
My solution:
Uninstall Chrome with clear personal data option selected
Install Chrome again but without admin right (install for your personal
user)
Use Chrome as normal

Unable to fetch iOS webapp files on manifest update. 401 unauthorized

I have a HTML5 webapp which is running perfectly when served via the IIS without authentication.
Is is using a cache.manifest file.
Both when running in safari, and as an "add to homescreen" fullscreen app, once I update the manifest file on the server, and the app will update.
When I turn on authentication on all files except the cache.manifest, then I only see the update when running it in the safari browser.
If I add it to the homescreen, I am not able to make the app update the cache.
If I wireshark the traffic on the server, I can see the manifest file is fetched without problems, but all the files in the manifest file hits a 401 Unautorized error.
Any idea how I can fix this? Running it in the safari browser is working..
Any help is highly appreciated.
Safari is much more aware of HTTP Basic Auth, but web.app (the home screen web app handler, which is basically a UIWebView wrapper) isn't as full-featured and doesn't appear to support basic auth.
It seems you may need to work around this with either a server-side solution to append an authentication key to the filename (such as application.css?longhexkey) to bypass basic auth, or go with a more traditional login form (which may require significant changes to your app)
Same issue on Sencha forums: Unanswered: Forcing re-authentication after offline usage on iOS devices?