Open obi-jon opened 7 years ago
The plugin is sending the data without a leading "/" in the URI, which will cause logstash to return a 400 Bad Request status.
Plugin currently sends -> POST burp-/issue
This produces an error in logstash
If the data is sent with a leading slash -> POST /burp-/issue then logstash accepts it.
As a follow up - This may be a non-issue. The application allows you to include the leading slash in the "Elasticsearch Prefix" Field which is translated directly into the URI request.
The plugin is sending the data without a leading "/" in the URI, which will cause logstash to return a 400 Bad Request status.
Plugin currently sends -> POST burp-/issue
This produces an error in logstash
If the data is sent with a leading slash -> POST /burp-/issue then logstash accepts it.