Stop passing facet names in URL (Coveo for Sitecore)

This is a bad practice since this allows manipulation of content on the page. See http://www.coveo.com/en/search#q=test&f:@fz95xtemplatename70925=[This%20is%20a%20bad%20idea]

  • Shanid Gafur
  • Nov 27 2015
  • Will not implement
I need it... Month
  • Attach files
  • Gabriel Jahn commented
    November 27, 2015 15:30

    This can lead to some really nasty inappropriate use scenarios! Get it locked down!!!

  • Nicolas Bordeleau commented
    November 27, 2015 18:59

    Thanks for the idea, we will see what we can do.

  • Shanid Gafur commented
    April 22, 2016 14:52

    Is there any reasoning behind why this will not be implemented?

  • Shanid Gafur commented
    April 22, 2016 14:54

    Is there any reasoning behind why this will not be implemented?

  • Joe Bissol commented
    April 22, 2016 17:05

    What about enabling the ability to have a whitelist of Facets?

  • Nicolas Bordeleau commented
    April 24, 2016 08:14

    This is deep in the design of the JS Search Framework, it also have many perks that our customers love: Url sharing, State and browser history tracking, etc.

    That being said, I totally get your point and would like to propose a workaround solution. You could add a checksum parameter in the url. This way you still get the benefits of using the url but if someone craft it's own chain of parameters the interface simply won't load it.

    We have plenty other solutions available if this one is not for you. I'll contact you privately to make sure we find one viable for you.

    Thanks