URLs in search queries for filtering broken

[joepio]

We have a query parameter for filters, which using the tantivy QueryParser syntax. However, that doesn't seem to support escaping URL characters (or perhaps it does, but I don't know how yet).

If tantivy won't fix this upstream, we'll have to look for a different approach. We could index the shortnames (i.e. serialize to JSON instead of JSON-AD). Additionally, we'll need to either 1) let the front-end use the shortnames too, or 2) let the server fetch the shortnames and use these after parsing a filter value.

Also, we don't test for this. Bad!

[joepio]

Seems like using URL values in the key does work, but we need to escape the colons and dots in the key using slashes, and use a phrase query ("") for the value

    #[test]
    pub fn test_special_chars_escaped() {
        let q_escaped_colons = r#"https\://example.com/test/bla:"https\://examplevalue.com/test""#;
        let res = make_query_parser().parse_query(q_escaped_colons).unwrap();
        println!("{:?}", res);
    }