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.

Sign up for GitHub

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

Jump to bottom

Reports fail when PDF generation request includes Transfer-Encoding HTTP header #20724

Closed
stacey-gammon opened this issue Jul 12, 2018 · 3 comments
Closed

Reports fail when PDF generation request includes Transfer-Encoding HTTP header #20724

stacey-gammon opened this issue Jul 12, 2018 · 3 comments
Assignees
@azasypkin
Labels
blocker bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead regression Team:Visualizations Visualization editors, elastic-charts and infrastructure v6.4.0

Comments

@stacey-gammon
Copy link
Contributor

stacey-gammon commented Jul 12, 2018 •
edited
Loading

On master, it seems I can no longer generate reports. Looking at #10353 it seems it may be an http/https issue. I am running es via yarn es snapshot --license trial and kibana with yarn start.

Trying to create a repor results in a [error][client][connection] Error: Parse Error error being spit out and the report just hangs there.
@stacey-gammon stacey-gammon added bug Fixes for quality problems that affect the customer experience :Sharing (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead labels Jul 12, 2018
@stacey-gammon stacey-gammon changed the title Chromium reports fail with [error][client][connection] Error: Parse Error Reports fail with [error][client][connection] Error: Parse Error Jul 12, 2018
@timroes
Copy link
Contributor

timroes commented Jul 12, 2018

The same is true for PhantomJS. Tested on master, Chrome Linux.

@azasypkin
Copy link
Member

It may be caused by #18951: I'm trying to figure that out at the moment.

@timroes timroes added the v6.4.0 label Jul 12, 2018
@stacey-gammon
Copy link
Contributor Author

Issue has to do with base path and new platform. Once #19261 is checked in we can add a test that verifies reporting works without the --no-base-path that would have caught this.

@azasypkin azasypkin self-assigned this Jul 12, 2018
@azasypkin azasypkin mentioned this issue Jul 13, 2018
Merged
@azasypkin azasypkin changed the title Reports fail with [error][client][connection] Error: Parse Error Reports fail when PDF generation request includes Transfer-Encoding HTTP header Jul 13, 2018
@timroes timroes added Team:Visualizations Visualization editors, elastic-charts and infrastructure and removed enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure PR sent :Sharing labels Sep 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@azasypkin azasypkin

Labels
blocker bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead regression Team:Visualizations Visualization editors, elastic-charts and infrastructure v6.4.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@timroes @azasypkin @stacey-gammon