Closed juanlang closed 8 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?
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.
A simpler solution is to treat localhost specially.
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.
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.