Equals character breaks pagination in web search
Description
Gliffy Diagrams
Activity
Show:
Richard Pijnenburg December 17, 2012 at 4:50 AM
No work will be done on the current logstash-web and will be replaced by Kibana ( www.kibana.org )
Currently there are 2 options.
1) Wait until Kibana is runnable from logstash.
2) Run kibana your self.
Philippe Weber August 22, 2012 at 4:24 AMEdited
I looked at this issue for logstash web previously but did not find the time to make a full pull request yet.
The problem is the encoding of the param values of the navigation link (@next_href, @prev_href etc).
I found that it's seems to be "common" in Rails too to encode query string values with
instead of the current in api_v1.rb
CorryH August 21, 2012 at 3:02 PM
Not sure, I do not have any equals in the dataset right now.
My guess would be no, since the URL is base64'd
Jordan Sissel August 21, 2012 at 7:11 AM
Do you see this problem with kibana, too? Or just logstash web?
Any instance of the equals character in the search string will break the search when the pagination buttons are used.
Specifically, the query is trimmed when it is submitted so the query "FOO BAR=80 BAZ" becomes "FOO BAR" when the second page is requested.
It looks like the escaping method being used does not escape the equals character...