Don't want to reinvent the wheel, but really the solution didn't work. in the network. So until I write, I would like to ask japanesemade.
You have a database, say, cars. According to the search request, consisting of about 4-5 fields, we derive a list of results
, then go to the 4th page in the search results. In the end in the URL we get something like this:www.autosite.com/catalog/?page=4¶m1=21¶m2=...
On this page we find what we need, and move on viewing
On the preview page of this object, it is necessary to perform, such as sending requests
using the form on this object. Ie to reload the page again.
Hence the question:
How to implement a more correct return to the search results, i.e. pulling yourself constantly in the URL string:
Moreover, can constantly change the search parameters added-removed, and the preparation and pulling a these parameters are somehow not very convenient. So far the only option I see is writing a layer that will handle any incoming URL request and constantly pass it on. But somehow it's not very nice...