Hi i have a website that was previously running on http and now on secure server https. When it was running on http, change in style sheet was effecting web page immediately. But now when i used secure server https, changes in style sheet are not being effected. I have used cloudflare SSL certificate.
I have tried on Mozilla Firefox and Google Chrome protected tabs. I also have tried by using Google Chrome developer tools. Both of these couldn't help me out of this.
How i can make my style sheet take immediate effect on webpages.
https://www.ludhianaweddings.com/
Thanks in advance...
If you have Cloudflare SSL on I expect you probably also have their caching switched on?
Within the Cloudflare dashboard for your domain go to "Caching", the first option will be "Purge Cache". For best performance you can click "Purge Individual Files" and enter the URL of the CSS file you are updating. Alternatively click the dropdown and purge everything.
While you're working you may want to enable Development mode so you can frequently change files without having to purge the cache. This is also in the "Caching" tab, under "Development Mode".
Related
Anytime I have dev tools open on localhost my cookies are deleted and I am redirected to the login page on every page load which means I cannot use dev tools to debug or get insight into my site. I have localhost setup with a valid SSL cert (self-signed) and the site works normally until I open dev tools. How do I fix or disable this new "security" or setting in chrome?
After lots of issues and trying out many different things I came across this post/answer
When adding a Javascript library, Chrome complains about a missing source map, why?
Turns out that when I opened Dev Tools it would request a CSS map and the request was being sent to a different firewall causing my application to require me to re-authenticate every time this resource was requested. Turning off the CSS source map option fixed the issue
https://i.imgur.com/qKyu744.jpg
This started happening just a few days ago. I can access the site on the same computer in Firefox. Not sure why it is telling me that the site is insecure, but that must be related. I tried ipconfig /flushdns, deleting my cookies, and disabling my firewall but none of those fixed it. Can't find any solutions online either so far. Using the latest Chrome update and Windows 10. Please help!
Edit: Solved my issue by installing this Windows update:
https://support.microsoft.com/en-us/help/4284835
It is possible that you might have deleted trusted certificates from chrome trust store (github CA SSL certificate is issued by DigiCert High Assurance EV Root CA ), where as in for other browsers the trust store must be a different location in your case.
To check above listed certificate present in Chrome trusted store or not, do the following
Open Chrome then Go to Settings => Manage Certificates - Click on it, when Certificates pop-up shows then check at' Trusted Root Certificates Authorities, if desired certificate is not present then import it.
For what it's worth, this is what worked for me:
Open up the start menu and search for and open "Internet Options".
Go to the "Connections" tab.
Click on "LAN settings".
Untick all the checkboxes (there are 3).
Click OK twice and then access https://github.com/ via Google Chrome.
The reason why it works on Firefox is because it has its own proxy settings. Google Chrome takes the proxy settings of the computer.
If you enter the website URL with www, it will work in chrome.
To avoid this you need to add another CNAME without www.
I am using MacOS and I had similar issue of accessing GitLab with Chrome, but no issue with Safari.
What helps me finally is: Setting -> Privacy and Security, and turn off "Use Secure DNS".
If CORS extension has been downloaded and enabled in the Chrome browser then disable the CORS(Allow-control-Allow-origin) extension. It will work..!
When I'm developing using Node's http2 library (which only supports HTTPS, not HTTP), when I open localhost in Chrome, I get a warning screen:
Your connection is not private
Attackers might be trying to steal your information from localhost (for example, passwords, messages or credit cards). Learn more
NET::ERR_CERT_AUTHORITY_INVALID
You have to click "Advanced" then "Proceed to localhost (unsafe)". It gets annoying having to do this during development.
I generated a cert and key for localhost use according to the instructions for Node's http2 module. Is there any way to generate them in such a way that Chrome would actually accept them for localhost? Or is there another easy way to get rid of this warning?
(I'm aware of the option of launching Chrome with --ignore-certificate-errors but I'd prefer not to do this for all websites.)
Try the following:
In Chrome, put in chrome://flags/#allow-insecure-localhost in the address bar.
Enable the option that says "Allow invalid certificates for resources loaded from localhost".
Restart Chrome, and it should allow the site.
You can also type thisisunsafe once you put focus on the website
There are two options you can use to get rid of this annoying thing, which are:
Temporarily Disable SSL Warning
You can go to Google Chrome, input chrome://flags in the address bar and press the Enter key to access advanced settings.
In the next step, find the "Allow invalid certificates for resources loaded from localhost" option and enable it. This method is the same as using --ignore-certificate-errors attribute on your Google Chrome shortcut. It disables the SSL warning for all sites.
It's just a temporary solution and I wouldn't suggest to use this frequently.
(I'm aware of the option of launching Chrome with
--ignore-certificate-errors but I'd prefer not to do this for all websites.)
Install SSL On Your Localhost with OpenSSL
You can install SSL on your localhost with OpenSSL. By using this method, your localhost can run HTTPS without any issue at all. The tutorial is quite long with detailed instructions, you can read it at here.
Source: Fix Your Connection Is Not Private Error In Your Browser - ByteBiteBit.com
I tried too many techniques but nothing works at last i find it while i was learning Webapi.
i was unable to visit to any side beacuse of showing the Error "Your Connection is not Private"......
THE REASON IS You have to enable SSL on your Browser and how you can do it let me share the link..
Just follow the steps
https://www.youtube.com/watch?v=4hb6iD3nP6g&list=PL6n9fhu94yhW7yoUOGNOfHurUE6bpOO2b&index=16
chrome://flags/#allow-insecure-localhost in the address bar.
set it to Enabled
relaunch chrome
result
I am creating a new web site, where I was redirecting HTTP traffic on port 80 to port 443, using certificates created by Certbot. I was using NginX as a reverse proxy for Apache2, so all requests for PHP scripts were to be served from Apache.
I encountered a problem, and decided to remove the HTTPS redirection, stop the Apache server, and start again from the beginning. In other words, I now had Nginx working on its own, and just on port 80.
When testing in Google Chrome 62.0.3202.75, I dutifully cleared the cache. Many times. However Chrome continued to redirect my requests for http://sub.domain.com/index.php to https://sub.domain.com/index.php, which of course failed. Other browsers were happy to download the index.php file, with no complaints.
It was only when I decide to restore the original default settings for Chrome that Chrome started to behave correctly again.
How is it that Chrome was determined to unilaterally perform a redirect that was no longer valid, even after emptying the cache? Is there a more powerful way (other than restoring settings their original defaults) of getting Chrome to let go of a page?
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.