I agree this is concerning. This should at least be more publicity about
this... maybe FAQ on escaping user queries. I chased through the details
and it appears macro expansion snuck in as part of the JSON Facet API,
SOLR-7214 for v5.1, even though it affects requests not related to the JSON
Hi Erik,
I only have snippets of logs from the user so my details are limited. I
could request the parameter value for you if you like. But since it's
coming out of some large Documentum repository, pretty much anything is
possible. ;-) Documentum may have attributes that also use similar
Karl -
There’s expandMacros=false, as covered here:
https://cwiki.apache.org/confluence/display/solr/Parameter+Substitution
But… what exactly is being sent to Solr?Is there some kind of “${…” being
sent as a parameter? Just curious what’s getting you into this in the first
place. But
Hi all,
I've got a ManifoldCF user who is posting content to Solr using the MCF
Solr output connector. This connector uses SolrJ under the covers -- a
fairly recent version -- but also has overridden some classes to insure
that multipart form posts will be used for most content.
The problem is
