By "real" I mean "really fully qualified", as in "ending in a dot".
Try this:
https://apache.org.
Take note of the final dot. (Try https://apache.org./foo if you like.) In any
case what you'll see is:
1) You get asked to accept an untrusted cert.
2) You get 400 Bad Request.
Thoughts? Comme
On Saturday 06 June 2015 09:56, Fred Morris wrote:
> [...]
> Thoughts? Comments? Worth reporting?
Somebody thought so. ;-) Bug 58007 has been filed.
--
Fred Morris
___
dns-operations mailing list
dns-operations@lists.dns-oarc.net
https://lists.dns-oar
Since learning what 'fully qualified' really means, I've assumed this falls
into an area of arcane trivia that many, if not most of the applications
built atop the DNS probably don't implement correctly. Nearly every time
this topic comes up at work it's due to a junior admin publishing
something.t
On Sat, Jun 6, 2015 at 3:46 PM, Eli Heady wrote:
> Since learning what 'fully qualified' really means, I've assumed this falls
> into an area of arcane trivia that many, if not most of the applications
> built atop the DNS probably don't implement correctly. Nearly every time
> this topic comes up
On 6/6/2015 10:56 AM, Fred Morris wrote:
> By "real" I mean "really fully qualified", as in "ending in a dot".
>
> Try this:
>
> https://apache.org.
>
> Take note of the final dot. (Try https://apache.org./foo if you like.) In any
> case what you'll see is:
>
> 1) You get asked to accept an
