[eluser]markowe[/eluser]
Thanks for this input. Yes, when I was designing the application I took a conscious decision to not have ALL my parameters in the URL. Parameters which are purely user-specific I decided to store via POST/user session, like the city, state where they live etc. so the URL would not get too cluttered. I can see the SEO etc. benefits of doing it as above, but you are effectively advocating re-enabling GET, which CI has disabled, right?
With CI "segment" URLs, my link would end up looking like: controller/method/state/city/category/manufacturer/product/page and probably a few more, plus a marker like "Any" where they are not specified, so I could end up with:
products/listing/CA/Any/Any/phones/Nokia/E71/12
I dunno, those URLs get way too long and ugly, but I suppose I wouldn't be the first!
I guess the immediate way round my dilemma would be to write an intermediate page which checks for a POST and flushes the cache entry for that page (not catered for by the core, but I think someone wrote a small extension that does this) and then redirects to the actual page. Not too keen on redirects, but maybe this would be easiest...