On Fri, 30 Jun 2006 04:23:51 +0700, Peter Lauri wrote:
> Is it possible to some how find out all cookies on a specific computer
> and their name and value? I assume not :)
The global array $_COOKIE should hold any cookie which is available to you
--
Hilsen/Regards
Michael Rasmusse
cookies are stored is dependant of the users browser
and platform. Try this by having MS IE and FF display all stored cookies -
I bet you would get a different picture.
--
Hilsen/Regards
Michael Rasmussen
http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE3E80917
--
PHP
cket=/path/to/mysqld.sock
--
Hilsen/Regards
Michael Rasmussen
http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE3E80917
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
PHP is designed to be used on the web
in browser so htmlspecialchars, in my opinion, is redundant.
--
Hilsen/Regards
Michael Rasmussen
http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE3E80917
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Sun, 18 Jun 2006 15:55:14 -0500, Rob W. wrote:
>
> Is there a way with my mysql query so that I can list the numbers in
> correct order?
>
In what way is this problem related to PHP?
Try a MySQL group instead.
--
Hilsen/Regards
Michael Rasmussen
http://keyserver.veridis.c
ple use the build-in exception
handler. The most sane advise would be this:
getMessage();
}
echo "done parsing xml";
?>
--
Hilsen/Regards
Michael Rasmussen
http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE3E80917
--
PHP General Mailing List (http://www.
nce you've
> done this, and your design helps you to make sure that this step can't be
> bypassed by the user, you're protected against SQL injection.
>
Or even better: Use only prepared statements.
--
Hilsen/Regards
Michael Rasmussen
--
l side effect is
that all characters which need exscaping is automatically handled by the
DBMS. E.g the string O'leary would not cause any problems.
Another argument is, that it theoretically should run faster.
--
Hilsen/Regards
Michael Rasmussen
-
e set before it is inserted into the query, so
> how does what you state above deal with this?
>
The idea is exactly not to do any queries dynamically generated based on
user input! In the rare cases where this is needed you should not
allow any unparsed input.
--
Hilsen/R
he users input where to be used in queries defined by the
design of the application!
I think you have misunderstod the concepts of making queries based on
user input. It is not the users who should create the query, all to should
do is provide the input to narrow down the quer
ee my reply to Pablo Gosse.
--
Hilsen/Regards
Michael Rasmussen
--
It was all so different before everything changed.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
.
>
Again, true.
> In a broader scope I would here consider to be user input ANY input
> which is not hard coded into the application, and any input which is not
> hard coded should be thoroughly examined before being used.
>
I agree.
--
Hilsen/Regards
Michael Rasmussen
--
Hi all,
Is recode broken in php4.3.3 on OpenBSD? When I try recode it returns an
empty string! The same string used in mb* and iconv performs as expected.
--
Hilsen/Regards
Michael Rasmussen
--
You would if you could but you can'
13 matches
Mail list logo