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

Read users aren't able to export search results as CSV #1492

Closed
joschi opened this Issue Jun 17, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@joschi
Contributor

joschi commented Jun 17, 2015

Non-admin users who try to export messages of a stream as CSV, only get a JSON document with the following content:

{"type":"ApiError","message":"HTTP 403 Forbidden"}

Refs #1478

@joschi joschi added the bug label Jun 17, 2015

@joschi joschi added this to the 1.1.3 milestone Jun 17, 2015

@joschi joschi self-assigned this Jun 17, 2015

joschi added a commit that referenced this issue Jun 17, 2015

@joschi joschi closed this in 1d67928 Jun 17, 2015

@Binford3000

This comment has been minimized.

Binford3000 commented Jun 23, 2015

With 1.1.3 I get an error with "Invalid range type provided." as the reason. Only when exporting from a stream. Standard search -> export is working. Do you need any more information?

Request information:

Method
    GET
Query

        relative=300
        sortField=timestamp
        q=54bfbb5d0cf2b56ecadd2bf4?rangetype=relativeTrk*
        fields=message,source
        sortOrder=desc

Referer
    https://<HOSTNAME>:1443/streams/54bfbb5d0cf2b56ecadd2bf4/messages?rangetype=relative&fields=message%2Csource&width=1883&relative=300&q=Trk*
Connection
    keep-alive
Accept
    text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
DNT
    1
Accept-Language
    de,en-US;q=0.7,en;q=0.3
Accept-Encoding
    gzip, deflate
User-Agent
    Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Host
    <HOSTNAME>:1443

Cheers,
Guido

@edmundoa

This comment has been minimized.

Member

edmundoa commented Jun 23, 2015

I could reproduce the behaviour @Binford3000 described in 1.1.3 and master.

@edmundoa edmundoa reopened this Jun 23, 2015

@edmundoa

This comment has been minimized.

Member

edmundoa commented Jun 23, 2015

I thought it's better to create a new issue for tracking this, closing this one again :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment