Urls not advertised

[G2020sudo]

I got the name.js example running and successfully advertised the demos eff website to a chrome browser on a client. However i could only get two .org websites to advertise on my client. .com sites like intel.com lenovo microsoft etc never made it to my chrome client. Is the proxy filtering these sites? How can this be debugged?

[G2020sudo]

To clarify i used the examples/url/name.js

[jeffprestes]

Hi @Gabe2004 ,

maybe your problem is not the sender but into the receiver. What are you using to detect? Meanwhile, please check the following:

• Is the final URL HTTPS?
• Is there a robots.txt file that bans us from crawling their pages?
• Is the domain on any spam/phishing lists?

99% of the time, if a URL is rejected, it is due to the first 2 items on this list.

I hope it helps.

-Jeff

[sandeepmistry]

I can't get https//www.intel.com to work with the Chrome widget on iOS. However https://www.example.com is working fine.

Note: if I use the Physical Web (PhyWeb) iOS app, intel.com works fine.

[G2020sudo]

@jeffprestes was correct about robots.txt. This was my guess at first and confirmed. However is there a way to advertise ignoring https and robots.txt requirements? We wont be able advertise a lot urls if not and not sure how useful this will be.

[G2020sudo]

@sandeepmistry i was advertising from a win 10 laptop while using my marshmallow phone. Both the physical web app and chrome gave same results.

[G2020sudo]

Phone was the client in this case

[jeffprestes]

Unfortunately @Gabe2004 the by the Physical Web definition (Google) it must be crawled and under HTTPS. There is no other way.

[don]

@Gabe2004 For debugging I use nRF Connect on Android. Although the Google apps reject your beacon, you can see the URI is being broadcast.

There's an nRF Connect for iOS too, but it only shows the raw bytes, rather than the decoded data.

[sandeepmistry]

@Gabe2004 any updates on this? Do things work if you use HTTPS URL's? Also have you tried @don's suggestion above?