search

google / u2f-ref-code

U2F reference implementations
BSD 3-Clause "New" or "Revised" License
585 stars 182 forks source link

Reference HTTP server in u2f-ref-code is out of date #9

Closed juanlang closed 8 years ago

juanlang commented 9 years ago

Reported by STMicro, the standalone reference server doesn't actually work at the moment. It should be fixed, or removed in favor of the GAE server.

arnar commented 9 years ago

The reference server is useful for simpler testing, since running a local GAE server requires the appengine SDK.

The problem is that it is hardcoded to use http://localhost:8080 as the appId, which does not work with the new eTLD+1 policy. Simplest solution is to make the user specify an appId on the command line, or in the code. Any better ideas?

sampaths commented 9 years ago

Command line settings like a fine idea no? On Oct 16, 2014 4:43 PM, "Arnar Birgisson" notifications@github.com wrote:

The reference server is useful for simpler testing, since running a local GAE server requires the appengine SDK.

The problem is that it is hardcoded to use http://localhost:8080 as the appId, which does not work with the new eTLD+1 policy. Simplest solution is to make the user specify an appId on the command line, or in the code. Any better ideas?

— Reply to this email directly or view it on GitHub https://github.com/google/u2f-ref-code/issues/9#issuecomment-59447814.

juanlang commented 9 years ago

A simpler solution is to treat localhost specially.

leshi commented 8 years ago

Closing this.

The u2f-ref-code standalone server doesn't work, but not for this reason. The bug described here I don't think is an actual bug.