Shawn, Have we received a couple of mentions of this? Or am I misremembering? Do we need to open a JIRA and change how logging.js works?
ERic > On Nov 30, 2022, at 11:44 PM, Shawn Heisey <apa...@elyograg.org> wrote: > > On 11/30/22 13:44, Matthew Castrigno wrote: >> Using SOLR 9.0 and the ScriptUpdatProcesor, it appears SOLR is erroneously >> adding " ,​ " in the middle of a string field. >> >> The script just logs the fields. If you compare the curl request with what >> is logged you see the addition of many instances of ,​ in the content >> field. > > This just happens on the logging tab of the admin UI. In the javascript file > at server/solr-webapp/webapp/js/angular/controllers/logging.js I found the > following line: > > event.message = event.message.replace(/,/g, ',​'); > > HTML character code 8203 is the unicode "zero width space" character. I > think the admin UI code is trying to make long comma separated lists in log > entries word-wrap better, and somehow the browser is treating that as literal > text rather than an HTML entity. This is NOT in the data being indexed, it > is just in the log. It's definitely a display bug, but doesn't affect the > data being indexes. > > Here you can see the same thing happening with my server running > 9.2.0-SNAPSHOT: > > https://www.dropbox.com/s/77yc9bovxwaauu6/solr-logging-html-8203.png?dl=0 > > I checked solr.log and that text is NOT there. I bet if you check solr.log > you will also find that it is not there. > > Requests to the URL in my screenshot that do not come from specific IP > addresses are blocked. Those requests never get beyond the reverse proxy. > > Thanks, > Shawn > _______________________ Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | My Free/Busy <http://tinyurl.com/eric-cal> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> This e-mail and all contents, including attachments, is considered to be Company Confidential unless explicitly stated otherwise, regardless of whether attachments are marked as such.
