in reply to How CGI works

This node falls below the community's minimum standard of quality and will not be displayed.

Replies are listed 'Best First'.
Re^2: How CGI works
by Happy-the-monk (Canon) on Feb 23, 2018 at 14:53 UTC

    if you stumble-upon a URL somewhere that contains the string, php, you can be 100% certain that what the web-server is doing is executing that PHP program

    This is so very wrong.

    It it were a file suffix indeed and the webserver configured to execute those pages with PHP, then that would work.
    That is a somewhat common thing, but not ubiquitous.

    Don't be so certain, as there are at least three biggish companies where ".php" web pages are run with perl and a templating engine.

    Cheers, Sören

    Créateur des bugs mobiles - let loose once, run everywhere.
    (hooked on the Perl Programming language)

      The original PHP was even written in Perl.

      CountZero

      A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

      My blog: Imperial Deltronics

        Apparently not.

Re^2: How CGI works
by Your Mother (Archbishop) on Feb 25, 2018 at 10:12 UTC

    To pile on what Happy-the-monk said, believing that a file extension—or, worse, a substring of a file or a URL—is some kind of guarantee of file content or server side action is a scrub's mistake and the kind of thinking that leads to broken code and potentially serious security problems.