Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

web service broken at "Perform a query" #144

Closed
pat1 opened this issue May 30, 2018 · 3 comments
Closed

web service broken at "Perform a query" #144

pat1 opened this issue May 30, 2018 · 3 comments
Assignees
Labels

Comments

@pat1
Copy link

pat1 commented May 30, 2018

http://myserver:8090/
click on "Perform a query" and my browser download about 800Mb of something .
The expected behaviour is the possibility to specify a query.

@pat1 pat1 added the bug label May 30, 2018
@brancomat
Copy link
Member

Just for the record, this bug seems still presenti in the current version (1.25)

@brancomat
Copy link
Member

Still present in 1.29

@spanezz
Copy link
Contributor

spanezz commented Dec 22, 2021

A long time a go, in a version far far away, "Perform a query" linked to a form where one could paste an arkimet query and download its results. The form has long since disappeared, and only the link remained.

arki-server also didn't make a distinction between GET and POST queries, so clicking on the link would cause the same result as querying all datasets without arguments.

I have now removed the link, and added a distrinction between GET and POST in arki-server, so get inadvertedly GET-ting a query link will return "405 Method not allowed" instead of performing a huge query.

This technically fixes the problem, assuming that the old form is not needed, and that the way to access arki-server is via arki-query.

If there is a real use case for querying arki-server via browser instead, let's map it into a new issue, then add/readd support for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants