RS URL protocol and port inferred

[GregTurner]

When the agent is retrieving the authorizations during Review Authorizations, it goes to the registrar passing previously known RS ID(s). In response, the Agent get tokens to call all the RS.

The tokens nor response have the protocol and port parts of the RS URL. I can infer the URL by prepending "http" and appending "8080". Did I miss something in the spec?

Please advise.

[dickhardt]

All RSes are required to be on HTTPS

So, yes, you can just preface with 'https" and you are fine when we are in production

If you are working against a local copy, then you will need to adjust accordingly

On Jan 20, 2013, at 4:29 PM, GregTurner notifications@github.com wrote:

When the agent is retrieving the authorizations during Review Authorizations, it goes to the registrar passing previously known RS ID(s). In response, the Agent get tokens to call all the RS.

The tokens nor response have the protocol and port parts of the RS URL. I can infer the URL by prepending "http" and appending "8080". Did I miss something in the spec?

Please advise.

—
Reply to this email directly or view it on GitHub.