I want to prevent my asp.net page from browser caching.
I apply tricks available on internet,So browser stop caching my page and every time request to server for page.
But problem is when i access my site through mobile like blackberry it cache my page and on back button press page access from its cache without ping to server.
I searched a lot but found nothing special.
One solution i found which said that mobile browser only stop caching when https request is made
Is that true or not?
Please help.
Here is a suggested method which works with mobile and desktop browser: Prevent browser caching of web pages in asp.net which works in all browsers (IE/Firefox..)
Related
I'm developing a web page using asp .net and have another application which is published in my host. I want to access to the application just from my page and the application is not accessible from other IPs.
I used iframe, but iframe is connecting client directly to the application which is not what I want. How can I handle this?
I think without some wierd code, this is not possible since the IFrame is client side calls. This will make a hard time for you to bypass.
A little side question is, why dont you want people to access you page directly on the domain / ip, when showing it in the iframe will still let people access the page?
I develop ASP.Net Web Application and host on IIS with http protocol, everything working fine.
When I change from http to https, web page never finish loading and the browser was died (The problem only occurs in some page. If I logged with Normal User role, page would work. If I logged with Manager role, the problem would occur.).
Please help me to find the root cause of the problem.
I test on chrome, and capture the screen as below
Here is my web.config
Our web app currently under development has authentication on all the pages.
We can deny a user access to any particular page but have found that if a user had previously opened the page that they can still access the page via the url. [Even if they log out and log in]
Assuming that the page is coming from client cache [Ctrl F5 in IE kicks in the proper authentication behavior or clearing the client cache]
A lot depends on how we have implemented the authentication but a quick fix on our side would be from within the admin section where we deny access to certain pages that we expire client cache for that page.
Is there a way to do this programmatically.
This would mean that client caching would continue to work as normal for all other users that still had access to the page in question.
You can add this line to your Page base class or any where in a specific page you want to disable caching on.
Response.Cache.SetCacheability(HttpCacheability.NoCache)
When you created a wcf service, hosted it in IIS and then opened service page in browser you will see a default wcf help page. This page says 'You've created a service'.
What do u do with page? Do u hide it? Or replace it with your own?
Thanks
I'm not even sure you CAN hide them; you have to be able to access the URL in order to invoke the service properly, and the .svc markups don't allow ASP content to be displayed instead of the basic metadata pages. I think the only way you could do it is with a service in front of IIS, evaluating requests and redirecting "naked" service requests to a catcher page.
Being able to browse to the page is a useful diagnostic and DIY tool. If you can see the page from the browser of the computer with the client software, then you should be able to connect to that service using the client software. So, unless you can think of a security or aesthetic reason why the page cannot be exposed in your production site, I'd just leave it be.
I have a web site that work with external Credit Card Processing (cybersource)
when user want to buy the webpage redirect to cybersource the user fill his details
and click buy, the page redirect to my web site and show this message
"the current web page is trying to open a site on your intranet do you want to allow this"
the user need to click yes or no how can i avoid this message to show up?
Thanks
My first thought - are you testing this with a server that is on your own intranet? If so then it's a spurious warning that doesn't require any action from you to change. I don't think that many end-users will be using your site from the same intranet as the production webserver. :-)