{"action":"closed","issue":{"url":"https://api.github.com/repos/google/physical-web/issues/785","repository_url":"https://api.github.com/repos/google/physical-web","labels_url":"https://api.github.com/repos/google/physical-web/issues/785/labels{/name}","comments_url":"https://api.github.com/repos/google/physical-web/issues/785/comments","events_url":"https://api.github.com/repos/google/physical-web/issues/785/events","html_url":"https://github.com/google/physical-web/issues/785","id":172331414,"number":785,"title":"PWS Behavior and Dynamic URLs","user":{"login":"angst7","id":228315,"avatar_url":"https://avatars.githubusercontent.com/u/228315?v=3","gravatar_id":"","url":"https://api.github.com/users/angst7","html_url":"https://github.com/angst7","followers_url":"https://api.github.com/users/angst7/followers","following_url":"https://api.github.com/users/angst7/following{/other_user}","gists_url":"https://api.github.com/users/angst7/gists{/gist_id}","starred_url":"https://api.github.com/users/angst7/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/angst7/subscriptions","organizations_url":"https://api.github.com/users/angst7/orgs","repos_url":"https://api.github.com/users/angst7/repos","events_url":"https://api.github.com/users/angst7/events{/privacy}","received_events_url":"https://api.github.com/users/angst7/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":13,"created_at":"2016-08-21T17:33:23Z","updated_at":"2016-10-18T14:52:53Z","closed_at":"2016-10-18T14:52:53Z","body":"I'm seeing an issue in which the PWS proxy servers are sending requests that don't appear to be on behalf of any client.  I don't know if this is related to the caching behavior issue #739 , but I don't think it is.  Here's the general flow of the issue:\r\n\r\nA beacon (physical web weather station) base64 encodes some data and makes a url:  https://r1pl.com/AAAAAQEt4fB~  for example.  A nearby phone sees this and generates a request via PWS to fetch the data.  These URLs update about every 5 minutes (chosen to prevent the cache issue from creating a bunch of duplicates).  The data is logged at the server as history.\r\n\r\nThe problem occurs when I turn off the beacon.  (Only one such beacon exists, currently) Requests -- apparently old requests -- of the correct form continue to arrive to the server from the PWS proxy servers even with no beacon transmitting this data.  There doesn't seem to be a clear pattern to which URLs are resent or when, but they continue to be for over 12 hours after turning off the beacon.  \r\n\r\nDoes the PWS proxy system continue to recheck old URLs without any prompting from a PW enabled app sensing the URL?  (It seems this is so)  Is this intended behavior?\r\n\r\nThanks."}}
{"actor":{"display_login":"mmocny"}}