so the problem i'm facing is the site works fine in firefox , and it even works fine while loaded on http in chrome, but when you switch to https it stops working and in network tab only returns the site url with 304 status and doesn't load anything, but then again when you switch to icognito mode in chrome it still works fine, i've already removed all my extensions and cleared my cache and site data and ...
but the problem still remains, the url for the site is below:
https://hichhop.com
http://hichhop.com
please test both urls in both chrome and firefox to get what i mean exactly,
thank you in advance.
On reloading the mentioned website and keeping an eye on the networks tab in developer mode , you can check that in normal mode , i.e. , not incognito one , the site crashes before the below warning comes whereas you can see the below warning in incognito mode .
Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure element ''. This request was automatically upgraded to HTTPS, For more information see
You can read more about this warning and how to resolve it using below link :
https://www.thesslstore.com/blog/how-to-find-and-fix-mixed-content-warnings-on-https-sites/
FYI , in incognito mode , insensitive and mixed content isn't blocked by default leading to your site opening in it .
Works fine for me, I think this may be an issue with your Chrome and STS
Browse to chrome://net-internals/#hsts
Under Delete domain security policies type hichhop.com and click Delete
Browse to chrome://settings/clearBrowserData
Check Cached images and files and click Clear data
Related
When browsing to http://localhost:8080/ in chrome I get redirected to a bad request page, provided by the chrome browser. If I browse to the network url ie: http://192.168.1.1:8080/, then the chrome browser happily loads it.
The localhost url works fine in Firefox and in Edge.
Has anyone experienced this behaviour before and know how to fix it?
Check your chrome proxy settings and hosts file, also try the guest and private mode.
It might be a cookies problem
Our application uses a popup window to show a report. This works in every browser except Chrome.
In Chrome the URL in the Network tab of the inspector has a blank response. I also see Chrome loading an inject.preload.js script from disk cache?
This exact same page works in Firefox and Safari as well. I haven't been able to check IE yet (i'm on a mac today).
What is this inject.preload.js script and why would Chrome not load a URL in a popup?
The exact same code running staging servers works, the popup loads just fine. In production it works everywhere except Chrome. Both staging and production use SSL, have the same config, etc.
I unfortunately can't link as its a secured site.
Inject.preload.js is generally some sort of adblocker. It could be the case that its acting up and blocking your popup. If it is the case, it would show as an icon to the right of the address bar.
Click Me
This used to work as a valid href attribute but it seems in the past few months it now shows an error in the console (I'm using Chrome):
Not allowed to load local resource: view-source: http://stackoverflow.com
I found some links from 2013 where this was once a bug in Chrome but said it was fixed.
Could someone point me to an authoritative source that can explain why this no longer works? I assume that this is security by the browser and not an angular issue (since view-source is whitelisted and used to work)
Looks like Chrome and Firefox (at least) disabled this within the past year or so
I found this thread, and these release notes explaining why and provides a timeline as to when the change took place.
Related StackOverflow question: File URL "Not allowed to load local resource" in the Internet Browser
Chrome responds with the "Not allowed to load local resource:" as a security protocol. I'm not sure why this used to work, but not now, though there is no real way around this unless web-security is disabled. There may be a different outcome on other browsers, but ultimately you are correct in thinking that it's Chrome's security.
The reason is that Chrome tries to preload URLs in background, to speed up your browsing experience.
If you open the DevTools after loading the page, the content of the items listed on the Resources tab may not be populated. This is also true of network requests on the Network tab. To see the fully populated resources on the Resources tab, first open the DevTools, then refresh the page, or navigate to the desired page with the DevTools open. Now select the html resource and it should be populated.
I tested this on multiple sites and I have the same problem everywhere. When I refresh the site in Chrome with developer tools open, the site stops and its stuck on loading. In developer tools opens the tab Sources with bundle.js file code and I get and error in console:
Cannot read property 'dataset' of null
Why is this error occurring and how can I resolve this? I tried to restart my computer but its not working. Disabling JavaScript in Chrome is not an option. I have Chrome Version 52.0.2743.116.
I'm setting up a local development server on my Mac using nginx in place of Apache. I'm basically there, but having one issue.
I have multiple web apps, and each are set up using sites-available and sites-enabled - no issues here. The issue is that my browser of choice is chrome, and there's some weird caching going on that is causing the first-visited app to load each time. For example, I have:
site1.dev
site2.dev
If I load site1.dev, it loads without issue. If I load site2.dev, it's automatically redirected to site1.dev. I see this as a caching issue because if I use chrome's Incognito mode, I don't have the same issues (nor do I have them in Firefox).
Does anyone know what could be going on here? Or what the solution could be? Thanks in advance!
The solution is to open Chrome's Dev tools (right click, inspect element), click the network tab, and disable caching. Reload the first url, and try the second url. If there is no redirect, disable caching, and the issue is resolved.
Chrome only redirects from cache if the page was initially loaded with caching enabled.