Fixed
Status Update
No update yet.
Comments
bo...@gmail.com
We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
js...@gmail.com
ar...@gmail.com
It's extremely frustrating that it's apparently now impossible on android 13 to write to data/obb without rooting devices. People hated this change in 11, hated it in 12, and now it's been done again. Please let us access the device we payed for. No one asked for this change.
Description
1. Try to fetch content via HTTP using a 'Accept-encoding: gzip" header.
2. Using the SDK, a 'Accept-encoding: identity' header is always sent instead.
Unfortunately, the Yahoo BOSS API rejects requests that include a 'Accept-encoding: identity'
header. The only way to use the API is to not include a 'Accept-encoding' header, or use
'Accept-encoding: gzip'
I encountered this problem while trying to run the example application here:
Does this problem exist with both the SDK app server and our production app servers?
Just the SDK.
What is the expected output? What do you see instead?
The expected output is to match what the production server does. At the very least, it should log
a warning message if it isn't sending the requested headers.
What version of the product are you using? On what operating system?
OSX. App Engine SDK 1.1.9.
Please provide any additional information below.
I dug into the App Engine SDK source, and the problem is that ‘accept-encoding’ is listed in
_UNTRUSTED_REQUEST_HEADERS in
/usr/local/google_appengine/google/appengine/api/urlfetch_stub.py — commenting that out
made it possible to run the code on the SDK. Clearly the production system is doing something
different.