mirror of
https://github.com/google/nomulus.git
synced 2025-05-15 00:47:11 +02:00
Derive RDAP link paths from the received query
The former method -- a config string -- was cumbersome, as each Nomulus system would have to configure the link base to its own URL. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=173567021
This commit is contained in:
parent
30bfcf9c55
commit
11a218f9c3
25 changed files with 88 additions and 64 deletions
|
@ -761,17 +761,6 @@ public final class RegistryConfig {
|
|||
return 100;
|
||||
}
|
||||
|
||||
/**
|
||||
* Base for RDAP link paths.
|
||||
*
|
||||
* @see google.registry.rdap.RdapActionBase
|
||||
*/
|
||||
@Provides
|
||||
@Config("rdapLinkBase")
|
||||
public static String provideRdapLinkBase(RegistryConfigSettings config) {
|
||||
return config.rdap.baseUrl;
|
||||
}
|
||||
|
||||
/**
|
||||
* WHOIS server displayed in RDAP query responses. As per Gustavo Lozano of ICANN, this should
|
||||
* be omitted, but the ICANN operational profile doesn't actually say that, so it's good to have
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue