Is it possible to get rid of the query parameters displayed with URL?

[eodumosu]

I have been customizing my javascript-based Search Engine (for desktop application via CD-distribution), using DHTML and Prototype Javascript Framework. I have come a long-way since then, and I am succeeding, so far. However, here is my next dilemma.

When I click the "Submit" button, my search results displays all query parameters in the URL. Is it possible to get rid of the query parameters displayed in URL?


In search.js, functions getParam(paramName) and getParamArrayInt(paramName) return the value of a get parameter that are concatenated with urlLink which is then displayed in the browser's url-locator.

Here is what my search urlLink looks like in my div tag:
file:///C:/index.html?zoom_query=figure&zoom_per_page=10&zoom _cat%5B%5D=-1&zoom_and=1&zoom_sort=0#sy_nr_s8_5

Here is what I want it to look like in the same div tag:
file:///C:/index.html?#sy_nr_s8_5

I basically want to strip of the concatenated "query string" parameters. I know it can be done because my desired ulLink still loads well if I manually delete the parameters. I have modified search.js (particularly those two functions) to no avail. Can some shed some light into this?

p.s. my app is CD-based not web-based

[David]

We offer a variety of technical solutions for searching documents on CD.

We don't know what customisations you have done, nor why you thought customisation was required. Nor do we know anything about the "Prototype Javascript Framework" you refer to. So providing support for your customised script is outside of the free support that we offer.

But as for the more general issue of removing all parameters from the search URL, we don't think this is practical. If you have a search form using a HTTP GET then the parameters will always appear in the URL. You might think that switching to HTTP post is the solution (because with a POST the parameters are not passed in the URL, and the URL looks short and clean). But using a POST causes other issues. For example the links that allow navigation between search result pages won't work as they rely on a GET.