Geek Answers Handbook

How do I make a back link?

I have a detailed page that is called from different places and has a nice readable url like

"www.mypage.com/product/best-product-ever".

The calling pages (product list) have a more complex URL:

"www.mypage.com/offers/category/electronic/page/1/filter/manufacturer/sony/sort/price" and

"www.mypage.com/bestseller/this-week".

How to make a back link from the detailed page to the list of called products?

  • I can not use javascript
  • I don't want to have the calling page in the url because it is long
  • I really need links between pages, no http-post
  • I can not use sessionstate

EDIT: Sessionstate is excluded because if there are 2 Windows open, they will share the same back information.

+4
source share
5 answers

As Lee said, use the referrer value:

<a href="<%= Html.Encode(Request.UrlReferrer.ToString()) %>">Back</a>

If you don’t need the URL in the link because it is too long, try running some simple compression algorithm by URL, display the compressed data as text in Unicode, and then add the compressed URL as a parameter to the redirection page for example:

 <a href="Redirect.aspx?u=compressed_url_goes_here">Back</a>
+4
source

How about using referrer header value?

+2
source

Here is a crazy idea that will require a fair one, but one that works and cannot be healthy for performance (depending on your users) .. but here we go:

Create a repository for caching ' ListResults ' (and plug it in so that it is stored in the database, for example, or just left it in memory on the server). In short, what this Repo can do is save a ListResult , which will include everything to save the state of the current view of the list that any given user is looking at. This may include routes and other values ​​.. but essentially everything you need to redirect a filtered and sorted list to this page.

When the ListResult element ListResult added to the repo, a small unique hash key is created that will be URL friendly - something like this "k29shjk4" - it is added to the element along with a date and time stamp.

ListResult are saved only from the moment the list leaves the default view (i.e. there is no filtering, sorting, and Page 1). This will help in a small increase in productivity.

Element

A ListResult never be used, but all the detailed actionlinks in a specific kind of list have a ListResult.Key hash value added to the route. So yes, it may end up as a querystring, but it will be short (url-friendly), and if you want to get more confused with the routes, you can tidy it up.

To navigate back to the list, you may need a new small controller that takes just the hash value of ListResult.Key and redirects / re-creates the state of the list view (paging, filtering and sorting included) from the search in the repo.

So, we have fulfilled the requirements so far: not a single calling page in the URL (in the sense that its not the whole page is just a hash search); no posting, no sessions, no js.

To stop the repo from ListResult to large (and it’s dangerous: if you save it to the database), you can use the ASP.NET background service to periodically trim the "old" routes with a timestamp .. and "extend" the life of routes that are constantly used, adding time to the mark of the ListResult when it is requested through the new controller. No need to stop the route indefinitely, if the user needs a permanent link to the list view, they can bookmark the route of the long list itself.

hope this helps somehow

+1
source

Do you have cookies?

If so, you can put it there or use it to create your own session state.

0
source

I think this is more like "Back to results" and then to the general link "<<back", because you expected the general back link to return to the genetic list, and not to the list of highly filtered files that you described , is not it?

I don’t know if this applies to your “no message” condition, but the only option I see is that the Detail action is POST-only ( [AcceptVerbs(HttpVerbs.Post)] ) and includes another parameter, for example string fullRoute which is converted to a "link" on the details page for "Back to Results". Overload the Detail action without the fullRoute parameter and overload the action as a GET action so that the POST value of fullRoute is not required (when users are ok with the "common" Back link). This should serve as “general” GET requests on the Details page, as well as a POST request that will contain a “Back to Results” link for the filtered list.

0
source

More articles:


All Articles