Reading the spec, I can’t see why not, wondering if anyone knew.

  • bamboo@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    4
    ·
    5 months ago

    Having not read the spec, if there are any requirements for HTTPS, you most certainly will need a domain name for the TLS certificate.

      • bamboo@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 months ago

        Right, it can be done, but would require a CA who supports that, not all do. For example, Let’s Encrypt doesn’t allow bare IP addresses. I was assuming the question about an IP address was raised due to aversion to purchase a domain name. If so, then TLS certificate is another cost to consider and if not using a domain name, then the main free option becomes unavailable.

    • kopper [they/them]@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 months ago

      there is a general “encrypted transport” requirement which in real world use mandates HTTPS (although it’s worded broadly to allow for onion services and whatnot which provide their own encryption outside TLS)