Reports cannot be generated using ultra long urls

[stacey-gammon]

You can use Kibana with super long URLs using the storeStateInSessionStorage but reports won't work because they use the fully qualified url in order to pass all the information to the server.

If we implemented #14455 then we'd have a work around and it should work for reports generated in view mode (reporting should arguably only be available in view mode anyway, since the object has to be saved and it shows up as it would in view mode).

[tsullivan]

You can use Kibana with super long URLs using the storeStateInSessionStorage but reports won't work because they use the fully qualified url in order to pass all the information to the server.

We're going to take this on as a short term task. The plan will be to use the same jobParams data and include it in a POST payload rather than the query string. The API will be able to work either way, but the UI will always include the jobParams as a field of POST payload data.

@stacey-gammon @kobelb Do either of you have recollection of any reasons why the POST URL for report generation has worked by including jobParams in the query string, rather than POST payload? Was it a Watcher limitation?

My thinking is that it happened accidentally because it wouldn't have been a problem with the original implementation, that parsed SavedObject data from Type and ID.

[kobelb]

Do either of you have recollection of any reasons why the POST URL for report generation has worked by including jobParams in the query string, rather than POST payload?

It was mostly precedent... It always bothered me, and I really wanted to change it, but I never got around to it.

[tsullivan]

We had some difficulty tracking various issues on this that are actually all the same problem.

I'm closing this as a duplicate of the more-visible #27728