New issue
Advanced search Search tips

Issue 642256 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Unable to open semi-secure PDF in Chrome Beta

Reported by pshirse...@gmail.com, Aug 30 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.80 Safari/537.36

Example URL:
http://54.214.21.163:81/Temp/ChromeTest.pdf

Steps to reproduce the problem:
1. Enter specified URL in chrome browser
2. Press enter key
3. 

What is the expected behavior?
The PDF file opens and view-able.

What went wrong?
Browser asks for password even if the PDF is not password protected.
Also, password protected PDFs are not getting opened when after entering valid password.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? N/A 

Did this work before? Yes In the Chrome current version 52

Does this work in other browsers? Yes 

Chrome version: 53.0.2785.80  Channel: beta
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 22.0 r0

This issue is observed in Chrome Beta Version 53.0.2785.80 beta-m.
 
ChromePdfIssue.png
76.3 KB View Download
Semi-secure means the PDF is having access to only Copy, Print and High Resolution Print
Cc: gov...@chromium.org
Components: -Blink Internals>Plugins>PDF
Labels: OS-Chrome OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Seems to only happen in Chrome 53, but not 52 or 54.
So can you confirm that the new Chrome stable version 53 be released with this fixes.

Comment 5 by gov...@chromium.org, Aug 30 2016

Cc: pbomm...@chromium.org
We're planning to cut M53 Stable RC today. Please try to resolve this ASAP if this is M53 Stable blocker.
Labels: Merge-Request-53
Status: Fixed (was: Untriaged)
Reverting the fix from https://bugs.chromium.org/p/pdfium/issues/detail?id=539&desc=2 causes this file to fail, applying the fix and it passes when opened with pdfium_test. So, this looks like a dup and we should merge https://pdfium.googlesource.com/pdfium.git/+/6f1025492801aaa93fca2c0ed7c40a3389ad8cd1 into M53
Justification, the CL landed in PDFium in July and has not had any issues and should be safe to merge. Without this fix PDFs with permissions attached will fail to open in Chrome.

Comment 8 by gov...@chromium.org, Aug 30 2016

Labels: -Merge-Request-53 Merge-Approved-53
Approving merge to M53 branch 2785 (CL - https://pdfium.googlesource.com/pdfium.git/+/6f1025492801aaa93fca2c0ed7c40a3389ad8cd1 ) based on comment #7. Please merge ASAP. Thank you.
Project Member

Comment 9 by bugdroid1@chromium.org, Aug 30 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/buildspec/+/833e9ee4d07987f1f73633d04d534ae8ef9dd626

commit 833e9ee4d07987f1f73633d04d534ae8ef9dd626
Author: Dan Sinclair <dsinclair@chromium.org>
Date: Tue Aug 30 16:16:23 2016

Labels: -Merge-Approved-53 merge-merged-2785
Per comment #9, this is already merged to M53 so removing "Merge-Approved-53" label and applying "merge-merged-2785" label.
Labels: TE-Verified-53.0.2785.89 TE-Verified-M53
Verified this issue on Windows-10, Ubuntu 14.04 and Mac OS 10.11.6 using chrome latest Beta M53-53.0.2785.89 by following steps mentioned in the original comment. Observed the pdf file is able to open with out any restriction. Hence adding TE-Verified label.

Note:
------
Tested the same on CrOS: Blaze device version:53.0.2785.87/8530.76.0 and observed issue still not fixed is this build. So will verify it again on latest build 53.0.2785.89 once it's available.

Thanks!
Screen Shot 2016-08-31 at 3.02.54 PM.png
77.3 KB View Download
Status: Verified (was: Fixed)
ChromeOS build 8530.96.0 / 53.0.2785.154

Sign in to add a comment