469,611 Members | 1,718 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,611 developers. It's quick & easy.

Browser history problems

I am working on an ASP.NET application that seems to be limiting browser
histories to only one entry. I am not using SmartNavigation on any of the
pages, and that is the only thing that I have seen in the documentation that
says it limits the browser history. The pages in the application are in a
single IIS folder, which is set up as an application and is NT password
protected and SSL encrypted, and has the HTTP headers set to expire the
pages quickly. I have turned off the page expiration to no avail, nor can I
find any settings on the VS project, ASPX pages, or IIS folder that have any
effect on this.

I am wondering if anyone knows what else might cause a single entry browser
list, and for that matter what else (if anything) would control or limit
browser histories through ASP.NET?
Nov 29 '05 #1
2 1746
> I am wondering if anyone knows what else might cause a single entry
browser list, and for that matter what else (if anything) would control or
limit browser histories through ASP.NET?
How about one page doing all the work? That would certainly limit the
browser history.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
If you push something hard enough,
it will fall over.
- Fudd's First Law of Opposition

<Sc*****@noemail.noemail> wrote in message
news:Oj*************@TK2MSFTNGP15.phx.gbl...I am working on an ASP.NET application that seems to be limiting browser
histories to only one entry. I am not using SmartNavigation on any of the
pages, and that is the only thing that I have seen in the documentation
that says it limits the browser history. The pages in the application are
in a single IIS folder, which is set up as an application and is NT
password protected and SSL encrypted, and has the HTTP headers set to
expire the pages quickly. I have turned off the page expiration to no
avail, nor can I find any settings on the VS project, ASPX pages, or IIS
folder that have any effect on this.

I am wondering if anyone knows what else might cause a single entry
browser list, and for that matter what else (if anything) would control or
limit browser histories through ASP.NET?

Nov 29 '05 #2
Hi Scott,

Generally serverside code or any http header won't be able to manipulate
the clientside browser behaviors. Most of them are done through clientside
scripts.(the smartNavigation is also done through some script and a
internal iframe...). As far as I know, we can also avoid additional
history entry when redirecting page by using the window.location.replace
script function.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
| From: "Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com>
| References: <Oj*************@TK2MSFTNGP15.phx.gbl>
| Subject: Re: Browser history problems
| Date: Tue, 29 Nov 2005 15:44:32 -0500
| Lines: 35
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
| X-RFC2646: Format=Flowed; Response
| Message-ID: <O1*************@tk2msftngp13.phx.gbl>
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| NNTP-Posting-Host: 65-113-65-130.dia.cust.qwest.net 65.113.65.130
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msft ngp13.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.dotnet.framework.aspnet:361600
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| > I am wondering if anyone knows what else might cause a single entry
| > browser list, and for that matter what else (if anything) would control
or
| > limit browser histories through ASP.NET?
|
| How about one page doing all the work? That would certainly limit the
| browser history.
|
| --
| HTH,
|
| Kevin Spencer
| Microsoft MVP
| .Net Developer
| If you push something hard enough,
| it will fall over.
| - Fudd's First Law of Opposition
|
| <Sc*****@noemail.noemail> wrote in message
| news:Oj*************@TK2MSFTNGP15.phx.gbl...
| >I am working on an ASP.NET application that seems to be limiting browser
| >histories to only one entry. I am not using SmartNavigation on any of
the
| >pages, and that is the only thing that I have seen in the documentation
| >that says it limits the browser history. The pages in the application
are
| >in a single IIS folder, which is set up as an application and is NT
| >password protected and SSL encrypted, and has the HTTP headers set to
| >expire the pages quickly. I have turned off the page expiration to no
| >avail, nor can I find any settings on the VS project, ASPX pages, or IIS
| >folder that have any effect on this.
| >
| > I am wondering if anyone knows what else might cause a single entry
| > browser list, and for that matter what else (if anything) would control
or
| > limit browser histories through ASP.NET?
| >
|
|
|

Nov 30 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

34 posts views Thread by Charles Douglas Wehner | last post: by
6 posts views Thread by David | last post: by
8 posts views Thread by Ed Jay | last post: by
reply views Thread by devrayhaan | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.