Return to search results. (PHP)?

Question

PHP

I don’t want to reinvent the wheel, but I can’t really find a solution on the net. Therefore, until I started writing my own, I would like to ask the habran population.
There is a database of, say, cars. For a search query consisting of approximately 4-5 fields, we display a list of results , then go to page 4 in the search results. As a result, we get something like this in the URL:
www.autosite.com/catalog/?page=4¶m1=21¶m2=...
On this page, we find what we need and go to view this object:
www.autosite.com/ view/id10001/
On the page for viewing this object, you must, for example, send an application through the form to this object. Those. reload the page again.
Hence the question:
How to implement a more correct return to the search results, i.e. dragging behind you constantly in the URL string:
?page=4¶m1=21¶m2=33¶m3=13&...¶m44=123
Moreover, search parameters can constantly change, be added or removed, and composing and dragging these parameters around is somehow not very convenient. So far, the only option I see is writing a layer that will process any incoming URL request and constantly pass it on. Although somehow it is not very beautiful ...

Answer 1

cookies ||
session ||
output_add_rewrite_var()

Answer 2

But what if you write search parameters in cookies? and then process them

Answer 3

Sessions, cookies?

Answer 4

>Unsubscribed above that this is not suitable, since within one session there may be N-number of search results
Sessions IMHO the best option. and than prevents to store in session an array (hash) with results of search?? or if they don't need to keep the variable somewhat and just overwrite it with each change in the search query???

Answer 5

1. take "?page=4¶m1=21¶m2=33¶m3=13&...¶m44=123"
2. pass through base64
3. push it as a hidden field into the page
4. …
5. Profit!

Answer 6

The only thing that came to mind in terms of separating the tabs of one browser is SessionStorage. But this is already JS and do-it-yourself. And it doesn't work everywhere.

Answer 7

And what if all this is kept in a hidden field of the order form? And take the value from Referer?

Answer 8

you can use AJAX and pass parameters via POST

Answer 9

Your use case describes a situation where it is best to use AJAX to submit a request, and return to the search via js:window.history

Answer 10

Variants with AJAX disappear immediately because it is not kosher, since work with mobile browsers is also required, and not everyone supports them;
The option with various requests in the session is the most interesting, and I thought about it, but still, with some paranoia, I decided that this is no longer possible, since there may be supposedly 20-30 search windows open and then we will fly out of the session limits (if not a simple site), but I wanted some universality ...
Thanks for the answers, but so far I have not seen a single acceptable solution.
I do not believe that no one thought about some kind of layer.

Answer 11

The search handler generates a result set of records, saves them (in whole or only id) in the session with the key (you can also save query parameters there, for example, md5 from the search string and redirect to something like /search?key=hash - according to history, you can walk for a while and the load on the database is less

Answer 12

that is your form is processed by the same page? Or is there an appeal to another and then redirection back?