debugging workbench

[nguyenm100]

Hey folks, occasionally I test a query on work-bench and get back a blank page. Whereas if I run the same query in console or even through /rdf4j-server/respositories/...?query=... , I get back a result. I've isolated one usecase down to a result set that produces a lengthy literal string that looks something like:

;2;117705.75;2;8397.79;2;14859696.49;2;17;5;12/25/1993;2;9.50000;2;117774.75;2;8716.19;2;14868094.22;2;18;5;11/25/1993;2;9.50000;2;118101.83;2;41315.68;2;14876810.38;2;19;5;10/25/1993;2;9.50000;2;118689.05;2;74175.34;2;14918126.15;2;20;5;09/25/1993;2;9.50000;2;119830.28;2;144154.96;2;14992301.52;2;21;5;08/25/1993;2;9.50000;2;120543.65;2;90109.62;2;15136456.42;2;22;5;07/25/1993;2;9.50000;2;120609.07;2;8264.36;2;15226566.02;2;23;5;06/25/1993;2;9.50000;2;120917.35;2;38940.31;2;15234830.41;2;24;5;05/25/1993;2;9.50000;2;121131.07;2;26995.83;2;15273770.75;2;25;5;04/25/1993;2;9.50000;2;121328.23;

I think it could be in the TupleQueryResultView as that's the last thing I see my TRACE logs (no errors).

I'm using 3.7.4

Any hints on how best to debug this? Could this be some settings with Tomcat? I saw something about utf-8/iso-8859-1 but I don't think that affects results.

Thanks

[nguyenm100]

problem appears to be in url-encode.xsl

#3676