Web-based WHOIS, https, redirects
All, As we al lknow, ICANN requires " ... and a web-based Directory Service at <whois.nic.TLD> providing free public query-based access... ". However, I'm currently struggling with the question whether there are any more detailed specifications with regards to this? Specifically, would ICANN allow a redirect from http: (port 80) to https: (port 443)? I understand that some of our fellow registry backend operators are doing this, but is there any word regarding this in ICANN documents? I couldn't find any. Can anyone point me into the right direction? Thanks, Alex
On Feb 14, 2017, at 8:00 AM, Alexander Mayrhofer <alexander.mayrhofer@nic.at> wrote:
All,
As we al lknow, ICANN requires " ... and a web-based Directory Service at <whois.nic.TLD> providing free public query-based access... ". However, I'm currently struggling with the question whether there are any more detailed specifications with regards to this?
Specifically, would ICANN allow a redirect from http: (port 80) to https: (port 443)? I understand that some of our fellow registry backend operators are doing this, but is there any word regarding this in ICANN documents? I couldn't find any.
Can anyone point me into the right direction?
Thanks, Alex
There might not be any... but as long as IETF and W3C standards are followed, you are on safe grounds. Rubens
There might not be any... but as long as IETF and W3C standards are followed, you are on safe grounds.
Well, i do remember that during the very very early days of Pre Delegation Testing (actually, the pilot PDT), we were rebuked because (afaik) a sequence of two redirects on the WHOIS servers. So, while IETF and W3C might make the law, it always depends on the interpretation of the laws by "SLA police" ;) Alex
participants (2)
-
Alexander Mayrhofer -
Rubens Kuhl