Assigned
Status Update
Comments
je...@libertynetworks.com <je...@libertynetworks.com> #2
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
[Deleted User] <[Deleted User]> #3
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.
bo...@google.com <bo...@google.com> #4
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"
"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"
[Deleted User] <[Deleted User]> #5
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
Description
Problem you have encountered:
As per the REST documentation here:
pathMatchers[].headerAction.responseHeadersToRemove[] it should be possible to remove headers from responses in any circumstance (i.e. both backend buckets and backend services). However, in the case of backend buckets this doesnt actually work.
Support suggested I raise this as a feature request, but I am raising it as a bug since the docs say its possible. Feel free to see this as a bug against the docs and then a feature to make it work.
What you expected to happen:
For Header actions to work with backend buckets.
Steps to reproduce:
Upload a YAML definition as follows (names are example):
name: gumwe001
description: 'URL Map for the assets site (both SSL and none)'
defaultService:
hostRules:
- hosts:
- '*'
pathMatcher: assets-pm
description: 'Match All Hosts'
kind: compute#urlMap
pathMatchers:
- name: assets-pm
defaultService:
pathRules:
- paths:
- /
service:
routeAction:
urlRewrite:
pathPrefixRewrite: /index.html
- paths:
- /*
service:
- paths:
- /test-redir
urlRedirect:
hostRedirect:
pathRedirect: /images
redirectResponseCode: 'TEMPORARY_REDIRECT'
httpsRedirect: true
stripQuery: true
headerAction:
responseHeadersToRemove:
- 'x-goog-generation'
- 'x-goog-metageneration'
- 'x-goog-stored-contentencoding'
- 'x-goog-stored-content-length'
- 'x-goog-meta-goog-reserved-file-mtime'
- 'x-goog-hash'
- 'x-goog-storage-class'
- 'Server'
headerAction:
responseHeadersToRemove:
- x-goog-generation
- x-goog-metageneration
- x-goog-stored-contentencoding
- x-goog-stored-content-length
- x-goog-meta-goog-reserved-file-mtime
- x-goog-hash
- x-goog-storage-class
- Server
tests: []
This will not work.
Other information (workarounds you have tried, documentation consulted, etc):
Note that a workaround was suggested by support to use routeRules - however routeRules dont work with backend buckets. Another solution would be to allow routeRules with backend buckets.