Closed xdxxxdx closed 10 months ago
Hi @xdxxxdx ,
Could you provide a total data dump from your mongo? (Through whatever medium possible) The issue seems to come from not escaping sensitive HTML characters. We'll investigate
Hello @Yalz , here is the full data dump :) mongo_dump_776.zip
This issue has been fixed. The problem was not escaping sensitive HTML characters in the url of fragments. These characters in the urls are now encoded.
Hello @WLefever-Cegeka @pj-cegeka , This issue occurs again on the version: ldes/ldes-server:1.4.0-SNAPSHOT The turtle file with what is in the content when pinging http://localhost:8080/kbo/by-name?substring=& substringbug.zip
Same issue occurs on : 2.0.0-SNAPSHOT Thanks
Substring fragmentation has been deprecated so this issue with escaping sensitive HTML characters in the url of fragments can't happen anymore.
A great done
That is very specific bug, only occurs to the
tree:Node
http://localhost:8080/kbo/by-name?substring=&
for substring fragmentations. I think it is an error when processing “&”。 This issue doesn't occur to other fragmented pages: e,g.Prerequitests:
Scenario:
Current result Brower to http://localhost:8080/kbo/by-name?substring=&, there is no triples indicating the current node is a
tree:Node
. e,g,But for any other fragmented pages e.g. http://localhost:8080/kbo/by-name?substring=c. it has
According to the Tree Spec: https://treecg.github.io/specification/#traversing
As In the page http://localhost:8080/kbo/by-name?substring= http://localhost:8080/kbo/by-name?substring=& is a
tree:node
of atree:Relation
There should be
In the whole RDF graph. The turtle file with what is in the content when pinging http://localhost:8080/kbo/by-name?substring=& substring_&.zip