[Discover] Context fails when document_id contains a slash

[kertal]

I bump into this issue in Kibana 7.8.0. I notice the document _id is the culprit.

• If the _id contains only alphanumerical characters, it will give me correct context and showing the surrounding url.
• if the _id contains the special character + or =, it works fine too.
• If the _id contains a slash /, it first converts the _id into html ASCII characters (with %2F) but then resolve into wrong url which subsequently causing "Failed to load anchor document" like this:

To check a surrounding document with id= v/xA69ZXhXRk21sWH56BNnwibvs=

It gives the url like:

https://my_kibana_url/app/kibana#/discover/context/my_index_pattern-*/v%2FxA69ZXhXRk21sWH56BNnwibvs%3D?<extra_filter>

Note the context changed into #xA69ZXhXRk21sWH56BNnwibvs= with missing v/

but it then resolves into:

https://my_kibana_url/app/kibana#/discover/context/my_index_pattern-*/xA69ZXhXRk21sWH56BNnwibvs=?<extra_filter>&type=v

Note the _id change and &type=v at the end of url.

• probably worth to check other special characters.

TL;DR, _id containing foo/bar gives url with context bar, with &type=foo appended in the url.

Originally posted by @Leaf-Lin in #50482 (comment)

[pradeepnnv]

@kertal , which Kibana release has this fix?

[kertal]

@pradeepnnv 7.10, our next release

[prabaharan0312126]

We ae using 7.8 elastic search. kibana 7.10.0 is not compatible with 7.8 elastic search.
is there any plan to fix this issue in a kibana release which is compatible with 7.8?

[kertal]

There are no plans to fix this below 7.10.0, sorry