in reply to HTTPS communication

That's handled by the web server (canonically Apache) and is totally transparent for Perl-CGIs. (unless your Perl is involved in serving, which I doubt)

Normal step is to create an SSL certificate for your domain and to make it accessible by the web server.

You might also need to update your rewrite rules, most sites nowadays "redirect" all http to https to disallow non-encrypted traffic.

The CGI won't notice any of this, neither in- nor output is different, except of course some HTTP-headers/ENV-Vars which have to be explicit about the URL.

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

Replies are listed 'Best First'.
Re^2: HTTPS communication
by harangzsolt33 (Deacon) on Nov 18, 2018 at 03:02 UTC
    Okay, thank you very much for your quick reply!!!

    So, and just to clarify things, if I ever use the URL to transfer data between the server and client, for example:

    https://www.mywebsite.com/hitcounter.pl?visits=314&screen_res=1024x768&browser=Chrome&os=Win10&r=49638251

    JavaScript requesting this image url, to count page hits, then that information in the URL will be visible to ALL others even though other data (content) is encrypted. Right?

      what?

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

      PS: good night! :)

        My web page talking back to the perl script revealing the screen resolution in this case for example would be a bad idea. So, I would have to rewrite some of my perl scripts to make them communicate differently.