Script running under Command Prompt or Browser or some otherapplicatio n?

[Ojas]

Hi!,

I just out of curiosity want to know how top detect the client side
application under which the script is getting run. I mean to ask the
how to know whether the script is running under Command Prompt or
Browser or some other application?

Ojas.

[Jerry Stuckle]

Norman Peelman wrote:

Jerry Stuckle wrote:

>Kailash Nadh wrote:

>>On Nov 28, 5:34 am, Ojas <contacto...@gm ail.comwrote:
Hi!,

I just out of curiosity want to know how top detect the client side
applicatio n under which the script is getting run. I mean to ask the
how to know whether the script is running under Command Prompt or
Browser or some other application?

Ojas.

Yep, when a php script is run from the commandline, the two variables
$argc and $argv (commandline arguments) are registered.
They might be empty, but they still would be registered when being run
from the commandline (and not when not in the commandline)
http://uk.php.net/features.commandline

--
Kailash Nadh | http://kailashnadh.name

But that's server side. He asked about client side. And the answer is
there is no good way.

If the OP is trying to determine weather the program is running via a
internet server/browser or command line (terminal) then check this out.

Either of these two lines will tell you:

echo PHP_SAPI."\n\r" ;

or:

echo php_sapi_name() ."\n";

...see: http://us.php.net/manual/en/features.commandline.php

---
Norm

That wasn't the op's question.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[Norman Peelman]

Jerry Stuckle wrote:

Norman Peelman wrote:

>Jerry Stuckle wrote:

>>Kailash Nadh wrote:
On Nov 28, 5:34 am, Ojas <contacto...@gm ail.comwrote:
Hi!,
>
I just out of curiosity want to know how top detect the client side
applicati on under which the script is getting run. I mean to ask the
how to know whether the script is running under Command Prompt or
Browser or some other application?
>
Ojas.

Yep, when a php script is run from the commandline, the two variables
$argc and $argv (commandline arguments) are registered.
They might be empty, but they still would be registered when being run
from the commandline (and not when not in the commandline)
http://uk.php.net/features.commandline

--
Kailash Nadh | http://kailashnadh.name
But that's server side. He asked about client side. And the answer
is there is no good way.

If the OP is trying to determine weather the program is running via
a internet server/browser or command line (terminal) then check this out.

Either of these two lines will tell you:

echo PHP_SAPI."\n\r" ;

or:

echo php_sapi_name() ."\n";

...see: http://us.php.net/manual/en/features.commandline.php

---
Norm

That wasn't the op's question.

I guess I took it to mean he might want to provide either a browser
interface or a terminal interface based on how the program was being
run. Possibly for scripts being run on the client machine. But i see
from the rest of the thread the true meaning of his question is now evident.

---
Norm

[AnrDaemon]

Greetings, Jerry Stuckle.
In reply to Your message dated Wednesday, December 5, 2007, 23:24:58,

>In reply to Your message dated Wednesday, December 5, 2007, 14:56:22,

>>As he said - if it is from the command line, $argc and $argv will exist,
as will $_SERVER['argc'] and $_SERVER['argv'].

Not if it is started using PHP-CGI and argc/argv vars disabled in
configuratio n.

If it's using php-cgi, then it's not started from the command line, is it?

You forgot that PHP-CGI *IS* a commandline executable intended to deal with
pipelined I/O from/to server.
And You still can use it instead of CLI (either knowing that or by accident).

JFYI:
<stdout>:php-cgi.exe --help
Usage: php [-q] [-h] [-s] [-v] [-i] [-f <file>]
php <file[args...]

[snip]
<stdout>:php.ex e --help
Usage: php [options] [-f] <file[--] [args...]
php [options] -r <code[--] [args...]
php [options] [-B <begin_code>] -R <code[-E <end_code>] [--] [args...]
php [options] [-B <begin_code>] -F <file[-E <end_code>] [--] [args...]
php [options] -- [args...]
php [options] -a

[snip]
Not a big difference, You see. Basically no difference in general,
same [-f <filename>] syntax for both versions of interpreter.
--
Sincerely Yours, AnrDaemon <an*******@free mail.ru>

[Jerry Stuckle]

AnrDaemon wrote:

Greetings, Jerry Stuckle.
In reply to Your message dated Wednesday, December 5, 2007, 23:24:58,

>>In reply to Your message dated Wednesday, December 5, 2007, 14:56:22,

As he said - if it is from the command line, $argc and $argv will exist,
as will $_SERVER['argc'] and $_SERVER['argv'].
Not if it is started using PHP-CGI and argc/argv vars disabled in
configuration .

>If it's using php-cgi, then it's not started from the command line, is it?

You forgot that PHP-CGI *IS* a commandline executable intended to deal with
pipelined I/O from/to server.
And You still can use it instead of CLI (either knowing that or by accident).

No, I didn't. CGI is NOT the same as CLI. CGI is started from a web
server. CLI is started from a command line. The processing and options
are not the same - which is partly why they have different names!

JFYI:
<stdout>:php-cgi.exe --help
Usage: php [-q] [-h] [-s] [-v] [-i] [-f <file>]
php <file[args...]

[snip]
<stdout>:php.ex e --help
Usage: php [options] [-f] <file[--] [args...]
php [options] -r <code[--] [args...]
php [options] [-B <begin_code>] -R <code[-E <end_code>] [--] [args...]
php [options] [-B <begin_code>] -F <file[-E <end_code>] [--] [args...]
php [options] -- [args...]
php [options] -a

[snip]
Not a big difference, You see. Basically no difference in general,
same [-f <filename>] syntax for both versions of interpreter.

Ah, but there are differences. And much more than your little --help
commands show. All they have is the command line options.
--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[AnrDaemon]

Greetings, Jerry Stuckle.
In reply to Your message dated Saturday, December 8, 2007, 05:36:28,

>>>In reply to Your message dated Wednesday, December 5, 2007, 14:56:22,

As he said - if it is from the command line, $argc and $argv will exist,
as will $_SERVER['argc'] and $_SERVER['argv'].
Not if it is started using PHP-CGI and argc/argv vars disabled in
configuratio n.

>>If it's using php-cgi, then it's not started from the command line, is it?

You forgot that PHP-CGI *IS* a commandline executable intended to deal with
pipelined I/O from/to server.
And You still can use it instead of CLI (either knowing that or by accident).

No, I didn't. CGI is NOT the same as CLI. CGI is started from a web
server. CLI is started from a command line. The processing and options
are not the same - which is partly why they have different names!

Go ahead and study basics, please.

Your statement "they are different because they are intended to use in
different way" is silly.

While a hammer and an axe is not the same, what makes the difference if I use
them both to hammer the nails in the wall with exactly equal success?

Remember: rock was not intended to be weapon, but Abel was killed by the Kain
throwed it.

>JFYI:
<stdout>:php-cgi.exe --help
Usage: php [-q] [-h] [-s] [-v] [-i] [-f <file>]
php <file[args...]

[snip]
<stdout>:php.e xe --help
Usage: php [options] [-f] <file[--] [args...]
php [options] -r <code[--] [args...]
php [options] [-B <begin_code>] -R <code[-E <end_code>] [--] [args...]
php [options] [-B <begin_code>] -F <file[-E <end_code>] [--] [args...]
php [options] -- [args...]
php [options] -a

[snip]
Not a big difference, You see. Basically no difference in general,
same [-f <filename>] syntax for both versions of interpreter.

Ah, but there are differences. And much more than your little --help
commands show. All they have is the command line options.

Show me any:

silly.php:
<?php

echo "General rant with personal attack\n";

?>

[C:\usr\sbin\php-5.2]$php.exe -f silly.php
General rant with personal attack

[C:\usr\sbin\php-5.2]$php-cgi.exe -f silly.php
General rant with personal attack

[C:\usr\sbin\php-5.2]$

Difference between CLI and CGI versions of executable is described in the
manual: CLI have forced to have argc/argv variables set and some other
things. NO OTHER difference than described in the manual.
--
Sincerely Yours, AnrDaemon <an*******@free mail.ru>

[Jerry Stuckle]

AnrDaemon wrote:

Greetings, Jerry Stuckle.
In reply to Your message dated Saturday, December 8, 2007, 05:36:28,

>>>>In reply to Your message dated Wednesday, December 5, 2007, 14:56:22,
>
>As he said - if it is from the command line, $argc and $argv will exist,
>as will $_SERVER['argc'] and $_SERVER['argv'].
Not if it is started using PHP-CGI and argc/argv vars disabled in
configurati on.
If it's using php-cgi, then it's not started from the command line, is it?
You forgot that PHP-CGI *IS* a commandline executable intended to deal with
pipelined I/O from/to server.
And You still can use it instead of CLI (either knowing that or by accident).

>No, I didn't. CGI is NOT the same as CLI. CGI is started from a web
server. CLI is started from a command line. The processing and options
are not the same - which is partly why they have different names!

Go ahead and study basics, please.

I have studied basics. Obviously a lot more than you have.

Your statement "they are different because they are intended to use in
different way" is silly.

Nope. CGI is not the same as CLI. And if you understood that you
wouldn't make the stupid claim that they are.

While a hammer and an axe is not the same, what makes the difference if I use
them both to hammer the nails in the wall with exactly equal success?

It makes a huge difference whether you're running PHP as a CGI or a CLI.
But you don't seem to understand that. Perhaps you don't even know
what CGI is.

Remember: rock was not intended to be weapon, but Abel was killed by the Kain
throwed it.

So what? Are you starting to troll, now?

>>JFYI:
<stdout>:ph p-cgi.exe --help
Usage: php [-q] [-h] [-s] [-v] [-i] [-f <file>]
php <file[args...]

[snip]
<stdout>:php. exe --help
Usage: php [options] [-f] <file[--] [args...]
php [options] -r <code[--] [args...]
php [options] [-B <begin_code>] -R <code[-E <end_code>] [--] [args...]
php [options] [-B <begin_code>] -F <file[-E <end_code>] [--] [args...]
php [options] -- [args...]
php [options] -a

[snip]
Not a big difference, You see. Basically no difference in general,
same [-f <filename>] syntax for both versions of interpreter.

>Ah, but there are differences. And much more than your little --help
commands show. All they have is the command line options.

Show me any:

You seem to know everything. You figure it out. Hint: find out what
"CGI" stands for.

silly.php:
<?php

echo "General rant with personal attack\n";

?>

[C:\usr\sbin\php-5.2]$php.exe -f silly.php
General rant with personal attack

[C:\usr\sbin\php-5.2]$php-cgi.exe -f silly.php
General rant with personal attack

Ah, now you're starting to troll. I made no personal attack on you.
But you've now started them.

[C:\usr\sbin\php-5.2]$

Difference between CLI and CGI versions of executable is described in the
manual: CLI have forced to have argc/argv variables set and some other
things. NO OTHER difference than described in the manual.

Try again. As I suggested before - figure out what CGI is. Then you
might have a clue.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[Jerry Stuckle]

Ojas wrote:

>
Hi!,

NC you have provided the list of all the available PHP SAPI but forgot
to mention when we can expect which is under existence?

Probably because that cannot be known in advance.

Also, this is very high level of intrusion being able to access the
site using CURL and socket. I can remember i access one of the site
using sockets to get the result of an particular operation to be shown
on interface of one of my project without even giving reference or
link to the output generator, of-course i would not like someone else
be able to do the same on my site. In that case how can i stop this
type of accessing?

Ojas.

That's the way the web works, and there's no way to stop it. If you
don't like it, don't use HTML. Create java applets, for instance,
instead. You'll lose a fair number of customers, but others won't be
able to use cURL. Or better yet, don't even put it on the web.

Of course, you'll lose all of the search engines, also. But heck -
you'll have your security.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[NC]

On Dec 9, 5:22 am, Ojas <contacto...@gm ail.comwrote:

On Dec 7, 8:54 pm, NC <[e-mail] wrote:

- aolserver
- activescript
- apache
- cgi-fcgi
- cgi
- isapi
- nsapi
- phttpd
- roxen
- java_servlet
- thttpd
- pi3web
- apache2filter
- caudium
- apache2handler
- tux
- webjames
- cli
- embed
- milter

NC you have provided the list of all the available PHP SAPI but
forgot to mention when we can expect which is under existence?

The names are fairly descriptive. "aolserver" , for example, means
that PHP is running under AOL Server.

Also, this is very high level of intrusion being able to access
the site using CURL and socket.

Er, and how do you think browsers access them? Through the same
sockets...

I can remember i access one of the site using sockets to get
the result of an particular operation to be shown on interface
of one of my project without even giving reference or link to
the output generator, of-course i would not like someone else
be able to do the same on my site. In that case how can i stop
this type of accessing?

You really can't. A socket program can be written to do anything a
browser does. About the only thing you can do is to obfuscate the
server-side logic by complicating the client side through the use of
Flash, Java applets, ActiveX controls, or AJAX.

Cheers,
NC

[AnrDaemon]

Greetings, Jerry Stuckle.
In reply to Your message dated Saturday, December 8, 2007, 07:28:22,

>Your statement "they are different because they are intended to use in
different way" is silly.

Nope. CGI is not the same as CLI. And if you understood that you
wouldn't make the stupid claim that they are.

Where I said that they are the same? Quote please, if You're not a troll.
I said that _they_ _can_ _be_ _used_ _the_ _same_ _way_ in the case mentioned
above - running scripts from commandline.
And without checking the SAPI used to run a script, You can't, in fact, be
sure that You are running under CLI or CGI interface. Other way, You can't (in
script) be sure You're running from commandline or started from server.
I saw many posts on forums discussing that "PHP is running almost fine on my
server but some glitches..." and that was the case of using CLI instead of CGI
executable.
If You want to say that it is impossible, good luck... but life isn't loose
it's colors just because You're blind.
--
Sincerely Yours, AnrDaemon <an*******@free mail.ru>

[Jerry Stuckle]

AnrDaemon wrote:

Greetings, Jerry Stuckle.
In reply to Your message dated Saturday, December 8, 2007, 07:28:22,

>>Your statement "they are different because they are intended to use in
different way" is silly.

>Nope. CGI is not the same as CLI. And if you understood that you
wouldn't make the stupid claim that they are.

Where I said that they are the same? Quote please, if You're not a troll.
I said that _they_ _can_ _be_ _used_ _the_ _same_ _way_ in the case mentioned
above - running scripts from commandline.
And without checking the SAPI used to run a script, You can't, in fact, be
sure that You are running under CLI or CGI interface. Other way, You can't (in
script) be sure You're running from commandline or started from server.
I saw many posts on forums discussing that "PHP is running almost fine on my
server but some glitches..." and that was the case of using CLI instead of CGI
executable.
If You want to say that it is impossible, good luck... but life isn't loose
it's colors just because You're blind.

CGI is not run from the command line.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===