Use url-caster.physical-web.org instead url-caster.appspot.com

[beaufortfrancois]

For the sake of consistency and homogeneity, I would love if we would use https://url-caster.physical-web.org instead of https://url-caster.appspot.com. What do you think? It would be as trivial as:

• Adding a Domain Name to GAE: https://appengine.google.com/deployment/newdomain?app_id=s~url-caster
• Updating URLS in iOS & Android Apps and PWS to point to the new URLs.

[mmocny]

On the surface this seems like a reasonable request. However, I think the physical-web.org domain should stay out of reference implementations, perhaps.

Specifically, the current PWS isn't official, its just someone one of our team members is running. There may be several official PWS pop up over time (i.e. by Google, by other companies..), and we expect clients to choose their own backend as they do a search engine.

I think I'm negative on this change for that reason. It would make it seem like its the one-true-PWS, which we don't want..

Either way, PWS is only ever interacted with by apps and tinkerers, so it wouldn't really get noticed.

[beaufortfrancois]

Let's close the issue then. Thanks for your explanation Michal!

[mmocny]

Having slept on this, I'm not sure I agree with my own advice :P

physical-web.org is nothing more than a reference, but its still silly to be using an appspot domain when the reference apps depend on it for functionality. I think we do communicate the state of the relationships between everything well enough in our docs.

I'll bring this up today and try to make the update.

[beaufortfrancois]

Any news?

[mmocny]

I don't have rights to do this, I'll bring it up today with Scott.

[beaufortfrancois]

(gentle ping)

[dinhvh]

We agree that it would be a nice to have (as long as the old URL still works).

[mmocny]

Working on it with Scott. Trouble with some of the config, but will vc it out this week.

On Mon, May 18, 2015 at 2:44 PM Hoà V. DINH notifications@github.com wrote:

We agree that it would be a nice to have (as long as the old URL still works).

— Reply to this email directly or view it on GitHub https://github.com/google/physical-web/issues/361#issuecomment-103168285 .

[mmocny]

Woot, service.physical-web.org and service-dev.physical-web.org are live!

See it in action:

curl -k -s -H "Content-Type: application/json" -d '{"objects":[{"url":"http://www.google.com"}]}' http://service.physical-web.org/resolve-scan

[scottjenson]

Very cool! Just noticed that the icon pointer is still using appspot:

"icon": "https://url-caster.appspot.com/favicon?url=http...

Separate issue?

[mmocny]

It is, but thanks for raising it.

[mmocny]

Damn, in process of fixing this, I realize that https is broken: service.physical-web.org and service-dev.physical-web.org!

Cannot update the url until those are fixed :(

[mmocny]

Scott can you take a scan at domains.google.org to see if we can fix this, maybe there is an option?

[dinhvh]

I guess you would need a SSL certificate (yay.)

[scottjenson]

Yeah, Matthew added HTTPS to PWDEMO.ORG and it was quite a process. He could help on Tuesday.

Scott

On Fri, May 22, 2015 at 3:16 PM Hoà V. DINH notifications@github.com wrote:

I guess you would need a SSL certificate (yay.)

— Reply to this email directly or view it on GitHub https://github.com/google/physical-web/issues/361#issuecomment-104787773 .

[dermike]

Just found out there's a .pw domain that might just be the perfect fit. ;) http://www.buy.pw

[scottjenson]

demo.pw is only $500.... ;-(

[matthewsibigtroth]

I'm happy to help with the cert purchase. Installing on our node servers was pretty straightforward, so hopefully the same applies to the pws server. :)

On Tue, May 26, 2015 at 6:37 AM, scottjenson notifications@github.com wrote:

demo.pw is only $500.... ;-(

— Reply to this email directly or view it on GitHub https://github.com/google/physical-web/issues/361#issuecomment-105525951 .

[mmocny]

Do we need a new cert for every domain, or every subdomain? Perhaps we just need to set up the PWS with existing certs?

[mmocny]

Also, which node server? Seems physical-web.org does a 302 redirect to http://google.github.io/physical-web/, which I assume is configured with google domains. https://physical-web.org is invalid.

[dinhvh]

I think we don't even have a cert for physical-web.org.

[matthewsibigtroth]

We purchased a standard cert for pwdemo.org, which is our domain that we're hosting our prototype/demo node servers on. Our cert does not support subdomains, but one can pay more for a wildcard cert that will support all subdomains, I believe.

On Tue, May 26, 2015 at 10:39 AM, Michal Mocny notifications@github.com wrote:

Do we need a new cert for every domain, or every subdomain? Perhaps we just need to set up the PWS with existing certs?

— Reply to this email directly or view it on GitHub https://github.com/google/physical-web/issues/361#issuecomment-105614391 .

[mmocny]

Makes sense, based on some quick reading, you have to purchase foo.com, . foo.com, *..foo.com etc.

On Tue, May 26, 2015 at 1:55 PM matthew sibigtroth notifications@github.com wrote:

We purchased a standard cert for pwdemo.org, which is our domain that we're hosting our prototype/demo node servers on. Our cert does not support subdomains, but one can pay more for a wildcard cert that will support all subdomains, I believe.

On Tue, May 26, 2015 at 10:39 AM, Michal Mocny notifications@github.com wrote:

Do we need a new cert for every domain, or every subdomain? Perhaps we just need to set up the PWS with existing certs?

— Reply to this email directly or view it on GitHub < https://github.com/google/physical-web/issues/361#issuecomment-105614391> .

— Reply to this email directly or view it on GitHub https://github.com/google/physical-web/issues/361#issuecomment-105618077 .

[scottjenson]

Can we close this out yet?

[mmocny]

I think we still need to add support for https but that's not being actively pursued at the moment.