in reply to Re^2: prevent perl script running from browser
in thread prevent perl script running from browser

One possibility is that you could examine the HTTP_REFERRER.

When called from a web page, this is usually set.

If your "server" calls do not set this, or set it to a specific valye, you could use this as a detection mechanism.

Your question is a little strange, so I will not comment on the relative in-security of this method.

                All power corrupts, but we need electricity.

  • Comment on Re^3: prevent perl script running from browser

Replies are listed 'Best First'.
Re^4: prevent perl script running from browser
by marto (Cardinal) on Oct 01, 2017 at 09:47 UTC

    You alter/assign referrer, either in perl scripting or browser plugin.

[reply]
      You alter/assign referrer, either in perl scripting or browser plugin.

      Yes, but that does not matter. The idea is that $ENV{'HTTP_REFERER'} is set to some nonsense only if running as CGI. Unfortunately, this is not entirely true. Clients can choose not to send a Referer header, so you might run a CGI with $ENV{'HTTP_REFERER'} not set. Using $ENV{'GATEWAY_INTERFACE'} should be reliable. It is set by the webserver, it is always set, and it is set to a constant value independent from the HTTP request.

      Alexander

      --
      Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
[reply]
[d/l]
[select]

        All of this seems moot to me. I can't think of a scenario where having something only to be run locally is hosted in this way.

[reply]

In Section Seekers of Perl Wisdom