New issue
Advanced search Search tips

Issue 737796 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 2
Type: Bug



Sign in to add a comment

S3 Signed URLs pointing to a PDF fail to download

Reported by swa...@semprehealth.com, Jun 28 2017

Issue description

Example URL:
https://s3-us-west-1.amazonaws.com/discountcards.semprehealth.com/swaraj/477638a15db1ea282c140666fcd1039069303bd111fc29c3926a1417d527e2dc.pdf?Expires=1530250697&Signature=f7MIe0ScSS%2F9H6o1wqk6KPIJz8s%3D&AWSAccessKeyId=AKIAI5D7TQLMLQENARJA

Steps to reproduce the problem:
1. On an iPhone, open Google Chrome
2. Go to https://s3-us-west-1.amazonaws.com/discountcards.semprehealth.com/swaraj/477638a15db1ea282c140666fcd1039069303bd111fc29c3926a1417d527e2dc.pdf?Expires=1530250697&Signature=f7MIe0ScSS%2F9H6o1wqk6KPIJz8s%3D&AWSAccessKeyId=AKIAI5D7TQLMLQENARJA
3. Red file icon appears, with text that says 'Download failed.' When you click, 'RETRY DOWNLOAD' in bottom right, same error occurs again

What is the expected behavior?
iOS Chrome opens PDF correctly

What went wrong?
For some reason, when iOS chrome tries to access a file linked via a signed S3 URL (https://boto3.readthedocs.io/en/latest/reference/services/s3.html#S3.Client.generate_presigned_url), chrome fails to download the file

I have confirmed the link works on: iOS Safari, iOS Firefox, Mac OSX Chrome, Mac OSX Safari, Mac OSX Firefox

Did this work before? N/A 

Chrome version: 59.0.3071.102  Channel: stable
OS Version: iOS10.3.2
Flash Version:
 
chrome-pdf-error.PNG
108 KB View Download

Comment 1 by eroman@chromium.org, Jun 29 2017

Cc: rdsmith@chromium.org
Components: UI>Browser>Downloads
@rdsmith: Does Chrome on iOS use our network stack code for downloading?
Cc: droger@chromium.org
I don't actually know.  I *believe* not (I think iOS moved off of our stack a while back for even non-webview related things) but I'm not absolutely sure.  

droger@: Do you know the answer to Eric's question?


Cc: dtrainor@chromium.org
+dtrainor also, for #1.

Comment 4 by droger@chromium.org, Jun 30 2017

I think this is a known issue for iOS.
We are using the Chrome netstack, but without the right cookies.

See related (internal) doc:
https://docs.google.com/document/d/1zH2RK0nQ-2-BItWnDdDduakX60DUcX6swyjc7IkAHo4/

And related  bug 709680 .

Comment 5 by droger@chromium.org, Jun 30 2017

Cc: eugene...@chromium.org
CC eugenebut
Labels: M-62
Owner: peterlaurens@chromium.org
Status: Assigned (was: Unconfirmed)
This is something that we should be able to fix in iOS 11. M62 is probably the earliest release which will use iOS 11 SDK, so adding it as a tentative target milestone.
Owner: ----
Cc: -rdsmith@chromium.org
Components: -Internals>Network
Labels: -M-62 M-66
Owner: mrefaat@chromium.org
This should be fixed by using WK cookie store.
Cc: mrefaat@chromium.org
Labels: -M-66 M-67 Proj-New-Download-Manager
Owner: ----
Status: Available (was: Assigned)
Labels: -M-67 M-68
Cc: -eugene...@chromium.org
Owner: eugene...@chromium.org
Status: Fixed (was: Available)

Sign in to add a comment