RDAP: Remove port43 element from JSON output

According to Gustavo Lozano of ICANN: "In the case of the RDAP profile (gTLD space), the “port43” element is not expected to be used, because Whois/43 tcp will be deprecated in the future." So it sounds like we should not include the port43 element for the moment.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=130017966
This commit is contained in:
mountford 2016-08-11 12:23:39 -07:00 committed by Ben McIlwain
parent 72894253ae
commit 0cab13e6d8
32 changed files with 43 additions and 71 deletions

View file

@ -76,7 +76,7 @@ public class RdapNameserverActionTest {
action.response = response;
action.requestPath = RdapNameserverAction.PATH.concat(input);
action.rdapLinkBase = "https://example.tld/rdap/";
action.rdapWhoisServer = "whois.example.tld";
action.rdapWhoisServer = null;
return action;
}
@ -121,9 +121,6 @@ public class RdapNameserverActionTest {
if (!map.containsKey("rdapConformance")) {
builder.put("rdapConformance", ImmutableList.of("rdap_level_0"));
}
if (!map.containsKey("port43")) {
builder.put("port43", "whois.example.tld");
}
if (!map.containsKey("notices")) {
RdapTestHelper.addTermsOfServiceNotice(builder, "https://example.tld/rdap/");
}