playframework / playframework/play1

PDF files all come out blank

Open
#1,315 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.6k
Forks
671
Avg merge
12d 15h
Merged PRs (30d)
1

Description

Play Version (1.5.x / etc)

1.5.1

Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)

Windows 10 / Ubuntu 14.04

JDK (Oracle 1.8.0_72, OpenJDK 1.8.x, Azul Zing)

1.8.0_181 / 1.8.0_222

Library Dependencies
Expected Behavior

Please describe the expected behavior of the issue, starting from the first action.

  1. Place a pdf file in the /public folder
  2. Serve it through the default "staticDir:public" route
  3. PDF should be displayed correctly in the browser
Actual Behavior

Please provide a description of what actually happens, working from the same starting point.

  1. PDF is served, but pages are all blank
Reproducible Test Case

This bug seems to have been introduced sometime since Play 1.2.6.2, PDF files were working correctly then.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by placing a PDF in /public and serving it through the default "staticDir:public" route on the listed Play and JDK versions. Then trace the static-file serving path and compare its PDF behavior with Play 1.2.6.2. Done means browser-served PDFs render their pages instead of appearing blank.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.