history length problem

[pentisia]

Hi there,
We are using history.go(integer) to go back to the certain page
directly. Because there are some pages interaction in between. For
example, starting from page 1 to page 2. From page 2, it will reload
sometime, or go to page 3 and then go back to page 2 again. If we use
history.back, it will only go back to the previous page. So, we have
to use history.go in order to go back to page 1 correctly.

But there is some problem with the history, sometime the history
will gone. For example, the history.length should record 10 pages,
but, it will show less than that sometime, likes 5 pages. And we found
out the pages before that are missing. Due to this, we can't go back
to the page 1 correctly as the pages had missing. We had figure out
this might cause by the size of that page that loaded. If the page
size is more, it will need more space to record to the history and the
pages that keep will be lesser.

We wish to know is there anyway we can change the setting to
enlarge the history size to keep more pages? We believe the setting
should be on the browser. But don't know where. We are using Internet
Explorer 6.0.

Thanks for the help in advance.

Best Regards,
Patricia

 

[RobG]

Hi there,
We are using history.go(integer) to go back to the certain page
directly. Because there are some pages interaction in between. For
example, starting from page 1 to page 2. From page 2, it will reload
sometime, or go to page 3 and then go back to page 2 again. If we use
history.back, it will only go back to the previous page. So, we have
to use history.go in order to go back to page 1 correctly.

But there is some problem with the history, sometime the history
will gone. For example, the history.length should record 10 pages,
but, it will show less than that sometime, likes 5 pages. And we found
out the pages before that are missing. Due to this, we can't go back
to the page 1 correctly as the pages had missing. We had figure out
this might cause by the size of that page that loaded. If the page
size is more, it will need more space to record to the history and the
pages that keep will be lesser.

We wish to know is there anyway we can change the setting to
enlarge the history size to keep more pages? We believe the setting
should be on the browser. But don't know where. We are using Internet
Explorer 6.0.

Thanks for the help in advance.

Do not try to use the history object to back to any particular page, it
is extremely unreliable - you can't be certain of how the user
navigated to the current page (as you've discovered).

 

[pentisia]

Hi there,
Is there any other way to go back to the page more accurately?
We are using VB.NET web application, we know "response.redirect"
can work fine but we have a problem that the pages in between are
actually from 2 different web project. For example, page 1 from web
project A go to page 2 from web project B. If we use
"reponse.redirect" without passing the http://, the page cannot be
found.
Thanks for your help again.

Best Regards,
Pat

 

[RobG]

Hi there,

Please don't top-post here, reply below a trimmed quote of what you are
replying to.

Is there any other way to go back to the page more accurately?

For some definition of "back", yes.

One method is to maintain 'bread crumbs' that indicate where in the
navigation model a user is at, and therefore they can jump back to some
earlier node in the tree. Another is to provide a navigation menu that
only provides suitable navigation links. JavaScript might be used to
save a server-side redirection, it certainly shoudn't be relied upon
entirely.

We are using VB.NET web application, we know "response.redirect"
can work fine but we have a problem that the pages in between are
actually from 2 different web project. For example, page 1 from web
project A go to page 2 from web project B. If we use
"reponse.redirect" without passing the http://, the page cannot be
found.

If you think it's a VB issue, then discuss it in a VB, .NET or IE
forum, not here. How you get the page into the browser is up to you -
discuss here what you get at the client, not the server.