I have a strange caching issue going on with IE9. The other day I set up a new website on my IIS server that was NOT running HTTPS, unfortunately I accidentally setup a redirect to HTTPS if you entered in HTTP. So because I didn't have it setup, the webpage didn't load becasue no HTTPS was running. I subsequently fixed the issue in IIS, and when I hit the web page with browsers other than IE9 it seems to work fine. For some reason in IE9 it just wont load the webpage (I think it is still trying to hit it on HTTPS).
I have tried clearing all temp files/cookies etc.., rebooted and still no luck. The only way I have been able to get IE9 to hit the web page was by going into 'F12 Developer Tools' and turn on "Always refresh from server" under the 'Cache' menu option. As soon as I turn that on it starts working. I turn it off and I cannot hit the website again.
Is there some other cache for IE9 that I don't know about that doesn't get cleared through normally processes?
I have a problem similar with yours. I fixed it by adding a random number in URL. Just like this: .....Index.asp?random=3283237431, hope this can help you.
Related
I have a website with Nuxt2, NetlifyCMS, and Vue2.
It has some media (animations, videos) and also connected to google analytics.
When I load the site from localhost, it goes up well, and when I switch pages through the nav bar, it works fine. However, when I type an address of one of the navbar pages in the URL (for example: localhost:3000/about), it gets stuck and chrome looks like it's loading but it's not doing anything actually.
The only thing that releases it, is closing the browser, and restarting the server (I cleared cache).
Any ideas why this is happening? I'm not getting any errors in the console.
I have developed cloud application in ASP.NET. After every deployment, the portal either shows white screen or shows older version of the application.
Any suggestions would be highly appreciated.
I have already tried:
1) Updating JS version in each deployment (white screen issue was resolved by this)
2) Recycling Application Pool
3) IIS manager->http response header->set common headers->enable web content
4) Restarting IIS(8.5) after each deployment
However, none of these have worked. The application works fine in incognito mode of Chrome browser but not the regular one.
However, none of these have worked. The application works fine in incognito mode of Chrome browser but not the regular one.
As far as I know, if your brower has accessed your web application once, it will store the cache in client side.
If you modify the content and add the response header, it will not re-send the request to the server, it will use the cache page.
To aovid this, the only way is clear the browser's cache or use Ctrl+F5 to refresh the page.
Then if your reponse haeder contains the no-cache next time, the browser will not store the cache again.
I am somewhat of a novice at debugging web traffic, so I am simply trying to understand what is going on.
I have fiddler and am using it to look at the network traffic being sent as I navigate to a specific website. I am noticing that the traffic picks up an HTTP 404 error thrown but I am still able to load the website.
Please help me understand how it still loads the website when it throws an HTTP 404 error? The error is never shown to the user. It is like it is ignoring it. I would think it would display the error to user and never load the website.
I have attached a picture of what I am seeing in Fiddler.
thanks
FiddlerTrafficwith404error
One of the reasons for this behavior is the browser stores the page in cache that is already loaded in browser once. Try opening the page in incognito/private mode (depending upon what your browser calls it) or try clearing your browser's cache and history.
I'm using PHP(header) to send a user back to the home page of the website(which looks different, due to a cookie, then when the user first arrived).
Everything works fine in Google Chrome but in Safari and FireFox a cached version of index.php is shown instead of the updated version of the webpage.
If I hit refresh things look as they should, but I need a way to tell the browser to reload the page without the user having to hit refresh.
Try this...
http://smartcoding.wordpress.com/2009/01/28/php-force-no-cache-page-load/
Our e-commerce site uses http for general site browsing to https for checkout. This process works in all browsers except for firefox. On firefox, we are seeing a an error that not all elements are secure.
Using forefox:
Go to http://www.creativecrash.com/marketplace/3d-models/vehicle/cars/sedan/c/seat-ibiza-2013-5door
click Add to Cart
click Checkout
Now the site should not be partially secure. If you click the icon beside the URL it should say "Your connection to this site is only partially encrypted, and does not prevent eavesdropping".
Now reload the page. It should suddenly be fully secure.
Any ideas on why this is happening and how we can fix it would be most appreciated.