search

google / physical-web

The Physical Web: walk up and use anything
http://physical-web.org
Apache License 2.0
6k stars 667 forks source link

URL not showing up #934

Open lucasbrechot1 opened 6 years ago

lucasbrechot1 commented 6 years ago

Hi,

I have deployed in partnership with a city organisation beacons equipped with physical web (Eddystone URLs) in the urban space in order to enable passengers to access citizen services. However although I can detect the beacons walking by, I do not detect the physical web urls on my phone.

An example url is: https://iotct.io/ClRa8

Do you know what is causing this problem?

Thank you for letting me know

ferencbrachmann commented 6 years ago

Hey, your URL does not validate with this unofficial validator: https://beaufortfrancois.github.io/sandbox/physical-web/url-validator/

ferencbrachmann commented 6 years ago

Every resource on the target URL has to have a valid https certificate! I suggest trying a specialized tool like Beeem for your beacon landing pages.

lucasbrechot1 commented 6 years ago

Hi!

Thank you very much for your reply! I am not clear what you mean by "Every resource on the target URL has to have a valid https certificate", does it mean that every link included on the landing page needs to be https?

bradmurray commented 6 years ago

No, every URL that it forwards to until the final page has to be https. So if you use a https://bit.ly to forward to an http://xyz.com page it will not accept it. I assume that the final page has to be a fully valid https page meaning there can be no http images or javascript on it.

ferencbrachmann commented 6 years ago

@bradmurray You are not correct. Any URL can be HTTP until the final URL. And every resource on the final URL (for example: images, css) has to be HTTPs. You can put http links into the page, but the page content has to be exclusively https.

lucasbrechot1 commented 6 years ago

@ferencbrachmann Understood! Thank you for the information!