html - Best practice for building a "Narrow your results" product filtering feature -
I am making the "narrow my results" feature and the best way to store the user's filter selection in that URL What is the practice that can be shared / bookmarked?
The clear selection is to keep all the user's selection in the query string only. However, both of these examples, some are much more secret:
Best Buy: http://www.bestbuy.com/site/olstemplatemapper.jsp?id=pcat17080&type= Page & amp; Cup = Krutktegoryid% 23% 23-1% 23% 23-1 ~~ q70726f63657373696e6774696d653a3e313930302d30312d3031 ~~ cabcat0500000% 23% 230% 23% 2311a ~~ cabcat0502000% 23% 230% 23% 23o ~~ nf518 || 24363030202d2024383939 & amp; List = y & amp; Nrp = 15 & amp; Sc = abComputerSP & amp; sp =% 2Bcurrentprice + skuid and usc = abcat0500000
It appears that they are telling a unique value for the search and are temporarily stored in their favor. Or maybe wrapping your DB ID into a bunch of garbage because they believe in security through ambiguity?
Is there some inherent harm to keep such things simple? www.mydomain.com?color=blue&type=laptop
So when I select the 17 "screen size as a filter, so that additional query page the will reload attack string: www.mydomain.com?color=blue&type=laptop&screen-size=17
Also, to clarify, I will probably use the related id to verify / parsing the database in the URL for easy / fast, but the question is whether there is some problem that will give me your simple Missing in Shtikon.
Thanks in advance!
Walmart ...). You may want to take a look at the check out. / P>
I do not think the URL structure has a lot of significance, but I really believe in presenting standards to readable One advantage of as to be dangerous. "Using guided discovery" is that you can produce the result set empty disallow invalid parameter combinations. If the query-string is user-editable, they may come in contact with invalid combinations, interrupting the search.
Comments
Post a Comment