Problem with access to the Rest_Api #2200

Myote · 2016-05-07T16:52:30Z

Problem description

Is there a problem in 2.0.0 with REST API browser ? Numerous timeout and I can't export to csv : {"type":"ApiError","message":"HTTP 404 Not Found"}

For the timeout I found the pb, it's when rest_enable_gzip = true; I removed it, but pb with export csv is always there.

My test configuration:
rest_listen_uri = http://0.0.0.0:12900/
rest_transport_uri = http://192.168.1.88:12900/
rest_enable_cors = true

rest_enable_gzip = true (comment to prevent timeout ...)

Steps to reproduce the problem

...

Environment

Graylog Version: 2.0.0-5 or 6
Elasticsearch Version: 2.3.2
MongoDB Version: 3.2.1
Operating System: RHEL 6.6
Browser version: all

kroepke · 2016-05-09T09:33:00Z

Which request are you executing? In general the API browser works in 2.0.

Could you provide a screenshot of the resources you see for the search API?

Myote · 2016-05-10T00:30:13Z

Hi Kroepke,

If one of this var 'rest_listen_uri = http://0.0.0.0:12900/' and '#rest_transport_uri = http:192.168.1.88:12900/' is filled with a reel ip and not 0.0.0.0, then 'Export as CSV' in main search page is broken because Graylog try to resolv an url with // (x.x.x.x//search/...).
If rest_enable_gzip = true is active then there is numerous timeout on x.x.x.x:12900/api-browser before the page is eventually displayed after many secondes.

I know, the title should have been problem with access to the Rest_Api and not ApiError ...

edmundoa · 2016-05-10T16:54:43Z

I can confirm there is a double slash in the generated URL to export the search results as CSV in certain situations. Will work on a fix for it.

In some situations, the `gl2ServerUrl` configuration option may end in a slash. As we can't predict when that will happen, this commit is normalizing the path of the generated URI, avoiding URIs with duplicated slashes in their path, as one of the issues described in #2200.

In some situations, the `gl2ServerUrl` configuration option may end in a slash. As we can't predict when that will happen, this change is normalizing the path of the generated URI, avoiding URIs with duplicated slashes in their path, as one of the issues described in #2200.

In some situations, the `gl2ServerUrl` configuration option may end in a slash. As we can't predict when that will happen, this change is normalizing the path of the generated URI, avoiding URIs with duplicated slashes in their path, as one of the issues described in #2200. (cherry picked from commit 70198f2)

jalogisch · 2016-07-19T16:03:00Z

@Myote could you please verify if this issue is still present in the present version?

please reopen if still present - until now i will close.

kroepke added the cannot reproduce label May 9, 2016

kroepke self-assigned this May 9, 2016

Myote changed the title ~~ApiError~~ Problem with access to the Rest_Api May 10, 2016

edmundoa mentioned this issue May 10, 2016

Normalize URIs #2213

Merged

jalogisch closed this as completed Jul 19, 2016

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Problem with access to the Rest_Api #2200

Problem with access to the Rest_Api #2200

Myote commented May 7, 2016 •

edited

kroepke commented May 9, 2016

Myote commented May 10, 2016 •

edited

edmundoa commented May 10, 2016

jalogisch commented Jul 19, 2016

Problem with access to the Rest_Api #2200

Problem with access to the Rest_Api #2200

Comments

Myote commented May 7, 2016 • edited

Problem description

rest_enable_gzip = true (comment to prevent timeout ...)

Steps to reproduce the problem

Environment

kroepke commented May 9, 2016

Myote commented May 10, 2016 • edited

edmundoa commented May 10, 2016

jalogisch commented Jul 19, 2016

Myote commented May 7, 2016 •

edited

Myote commented May 10, 2016 •

edited