Blobstore downloads have unknown size now that the Content-Length header is disallowed [35888819]

Bug

More Info Required

Status Update

No update yet.

Description

co...@gmail.com

created issue #1

Dec 27, 2010 02:40AM

According to the "Disallowed HTTP Response Headers" section in the Python Response class documentation here:

http://code.google.com/appengine/docs/python/tools/webapp/responseclass.html#Disallowed_HTTP_Response_Headers

the Content-Length header can no longer be set for "security purposes." Without being able to set that header, though, all blob downloads now have unknown lengths, causing all major browsers show unknown length progress indicators. This is an extremely undesirable state of affairs for the large and lengthy downloads which my app provides.

To solve this problem previously, I used the size field of the BlobInfo records in the datastore to set the Content-Length header directly, but now that this is no longer allowed, I am without recourse.

The following bug is related, but is not a solution to this problem:

http://code.google.com/p/googleappengine/issues/detail?id=2719&q=content-length&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log

Comments

ni...@google.com <ni...@google.com> Jan 19, 2011 11:42PM

Assigned to ni...@google.com.

[Deleted User] <[Deleted User]> #3Sep 22, 2011 01:49PM

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

ej...@evanjones.ca <ej...@evanjones.ca> #4Oct 1, 2011 08:32PM

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

pe...@pepto.de <pe...@pepto.de> #7Apr 30, 2013 02:21PM

Note that I've been able to make it work by:

Adding <action android:name="com.google.android.gms.wearable.BIND_LISTENER" /> in the intent filter
Removing <data android:scheme="wear" android:host="*" />

But I feel like this is not something we should do

[Deleted User] <[Deleted User]> #8May 6, 2013 06:03PM

I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨

jj...@gmail.com <jj...@gmail.com> #9Mar 25, 2014 01:27PM

If you're not targeting API 33 you're not affected by the bug. So it's a big bug, and yes we of course expected more from Google, but you can always target the api level later when it's fixed.

But I agree this is kind of desperating that more than 1.5 month after the first report nothing has changed.

sr...@gmail.com <sr...@gmail.com> #10Aug 15, 2015 12:32PM

As an interim update on this issue: we've been already working on the fix that should be available by Android 13 release. The fix requires thorough testing, I'll keep this bug updated as soon as we have more to share. Thanks!

ni...@daskalou.com <ni...@daskalou.com> #13Jan 30, 2017 02:43AM

I have no words for this. Android 13 is labeled "stable" but the Wearable API just doesn't work. Can't this issue be given higher priority? If you want to push WearOS you need to make sure it works normally.

is...@google.com <is...@google.com> May 11, 2018 07:44PM

Status: New