Jônatas Zechim wrote:
Hi..
You need to use $_FILES (
http://php.net/manual/pt_BR/reserved.variables.files.php)
Regards,
Jônatas Zechim
Thanks guys.
Donovan
--
D Brooke
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, 2011-08-02 at 10:04 -0500, Donovan Brooke wrote:
> Hello!,
>
> I must not be understanding something as I would expect 'f_file'
> to show up in the print_r below.:
>
> ---form--
>
>
>
>
>
>
> ---endform--
>
> --index.php--
>
> --/index.php--
>
>
>
>
> The result I
On 2 August 2011 16:11, Richard Quadling wrote:
> On 2 August 2011 16:04, Donovan Brooke wrote:
>> Hello!,
>>
>> I must not be understanding something as I would expect 'f_file'
>> to show up in the print_r below.:
>>
>> ---form--
>>
>>
>>
>>
>>
>>
>> ---endform--
>>
>> --index.php--
>>
On 2 August 2011 16:04, Donovan Brooke wrote:
> Hello!,
>
> I must not be understanding something as I would expect 'f_file'
> to show up in the print_r below.:
>
> ---form--
>
>
>
>
>
>
> ---endform--
>
> --index.php--
>
> --/index.php--
>
>
>
>
> The result I get is:
>
>
Le 02/08/2011 17:04, Donovan Brooke a écrit :
Hello!,
I must not be understanding something as I would expect 'f_file'
to show up in the print_r below.:
--index.php--
--/index.php--
try *:
*
;)
Hi..
You need to use $_FILES (
http://php.net/manual/pt_BR/reserved.variables.files.php)
Regards,
Jônatas Zechim
PHP & jQuery specialist
http://zechim.com
mob +55 11 7053 2239
skype ID zechim
On 2 August 2011 12:04, Donovan Brooke wrote:
> Hello!,
>
> I must not be understanding something a
Guys - the problem has been solved.
Give it a rest.
(sent only to the list)
(remainder deleted for the benefit of all :) )
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Thursday, 14 April 2011 at 23:08, Nathan Nobbe wrote:
On Thu, Apr 14, 2011 at 2:53 AM, Stuart Dallas wrote:
> > On Thursday, 14 April 2011 at 07:11, Nathan Nobbe wrote:
> > On Wed, Apr 13, 2011 at 3:30 PM, Stuart Dallas wrote:
> > > > On Wednesday, 13 April 2011 at 19:47, Nathan Nobbe wrote:
On Thu, Apr 14, 2011 at 2:53 AM, Stuart Dallas wrote:
> On Thursday, 14 April 2011 at 07:11, Nathan Nobbe wrote:
> On Wed, Apr 13, 2011 at 3:30 PM, Stuart Dallas wrote:
> > > On Wednesday, 13 April 2011 at 19:47, Nathan Nobbe wrote:
> > > I never make any assumptions about the source of any data
On Thursday, 14 April 2011 at 07:11, Nathan Nobbe wrote:
On Wed, Apr 13, 2011 at 3:30 PM, Stuart Dallas wrote:
> > On Wednesday, 13 April 2011 at 19:47, Nathan Nobbe wrote:
> > I never make any assumptions about the source of any data when I'm
> > developing software, whether in PHP or not. Retur
On Wed, Apr 13, 2011 at 3:30 PM, Stuart Dallas wrote:
> On Wednesday, 13 April 2011 at 19:47, Nathan Nobbe wrote:
> > On Wed, Apr 13, 2011 at 12:34 PM, Stuart Dallas wrote:
> > > On Wednesday, 13 April 2011 at 19:15, Nathan Nobbe wrote:
> > > On Wed, Apr 13, 2011 at 12:04 PM, Stuart Dallas
> w
On Wednesday, 13 April 2011 at 19:47, Nathan Nobbe wrote:
> On Wed, Apr 13, 2011 at 12:34 PM, Stuart Dallas wrote:
> > On Wednesday, 13 April 2011 at 19:15, Nathan Nobbe wrote:
> > On Wed, Apr 13, 2011 at 12:04 PM, Stuart Dallas wrote:
> > > > On Wednesday, 13 April 2011 at 18:55, Nathan Nobbe w
Nathan Nobbe wrote on 04/13/2011 12:47:11 PM:
[much snippage]
> no, it's actually a better practice. users are expected to populate
arrays
> they create. the $GLOBALS array is expected to be populated by user
> scripts. The $_POST array is expected to be populated by PHP. by the
time
> you
PHP then is Truly an amazing and powerful language. I can expand the
contents of the array $_POST by simply assigning a separate arry to it.
Obviously if I have a duplicate element-name in my array it will override
the $_POST element but that's my problem.
"Stuart Dallas" wrote in message
ne
On Wed, Apr 13, 2011 at 12:34 PM, Stuart Dallas wrote:
> On Wednesday, 13 April 2011 at 19:15, Nathan Nobbe wrote:
> On Wed, Apr 13, 2011 at 12:04 PM, Stuart Dallas wrote:
> > > On Wednesday, 13 April 2011 at 18:55, Nathan Nobbe wrote:
> > > On Wed, Apr 13, 2011 at 11:49 AM, Jim Giner <
> jim.g
On Wednesday, 13 April 2011 at 19:15, Nathan Nobbe wrote:
On Wed, Apr 13, 2011 at 12:04 PM, Stuart Dallas wrote:
> > On Wednesday, 13 April 2011 at 18:55, Nathan Nobbe wrote:
> > On Wed, Apr 13, 2011 at 11:49 AM, Jim Giner
> > wrote:
> > >
> > > > Can one create a set of $_POST vars within a sc
tp://3ft9.com/
> - Original Message -
> From: "Stuart Dallas"
> Newsgroups: php.general
> To: "Jim Giner"
> Cc: "PHP General"
> Sent: Wednesday, April 13, 2011 1:59 PM
> Subject: Re: [PHP] $_POST vars
>
>
> >
> > No
Shrug, it's called reply-all and it's been brought up here before :)
-nathan
On Wed, Apr 13, 2011 at 12:25 PM, Jim Giner wrote:
> No need to email me AND send to the list. Is that the standard practice on
> this forum? Not encountered it before.
>
>
No need to email me AND send to the list. Is that the standard practice on
this forum? Not encountered it before.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, Apr 13, 2011 at 12:04 PM, Stuart Dallas wrote:
> On Wednesday, 13 April 2011 at 18:55, Nathan Nobbe wrote:
> On Wed, Apr 13, 2011 at 11:49 AM, Jim Giner >wrote:
> >
> > > Can one create a set of $_POST vars within a script or is that not
> do-able?
> > > My display portion of my script u
When you say "assign that array to $_POST" do you mean
$_POST = $qrslt;
Not sure about this "assigning an array" thing.
- Original Message -
From: "Stuart Dallas"
Newsgroups: php.general
To: "Jim Giner"
Cc: "PHP General"
Sent: W
On Wednesday, 13 April 2011 at 18:55, Nathan Nobbe wrote:
On Wed, Apr 13, 2011 at 11:49 AM, Jim Giner wrote:
>
> > Can one create a set of $_POST vars within a script or is that not do-able?
> > My display portion of my script utilizes the POST array to supply values to
> > my input screen - this
Hi Jim,
Sure you can create set of et of $_POST vars :
e.g.
So that admin_code var is passed to myphpaction.php as post and shall be
access there via $_POST["admin_code "];
However, note that in PHP all the output buffer is flushed actually,
ONLY after the script execution is termina
On Wednesday, 13 April 2011 at 18:56, Jim Giner wrote:
And that includes adding entirely new elements in that array?
Yes, it's a standard array. It's not special other than being a superglobal.
> Do you have any suggestion on how to get the results of a query into POST
> easily or is it simply a
On Wed, Apr 13, 2011 at 11:49 AM, Jim Giner wrote:
> Can one create a set of $_POST vars within a script or is that not do-able?
> My display portion of my script utilizes the POST array to supply values to
> my input screen - this works well for the first display of an empty screen,
> and any fol
On Wed, Apr 13, 2011 at 1:49 PM, Jim Giner wrote:
> Can one create a set of $_POST vars within a script or is that not do-able?
> My display portion of my script utilizes the POST array to supply values to
> my input screen - this works well for the first display of an empty screen,
> and any foll
On Wednesday, 13 April 2011 at 18:49, Jim Giner wrote:
Can one create a set of $_POST vars within a script or is that not do-able?
> My display portion of my script utilizes the POST array to supply values to
> my input screen - this works well for the first display of an empty screen,
> and any
At 6:07 PM -0600 3/12/11, Shawn McKenzie wrote:
On 03/12/2011 10:37 AM, tedd wrote:
> Here's a demo:
> http://php1.net/b/form-radio1/
> Don't make it more complicated than it needs be.
My point exactly! So long as the name of the name[] part is the same
they will be treated as the same
On 03/12/2011 10:37 AM, tedd wrote:
> At 9:28 PM +0200 3/11/11, Danny wrote:
>> Hi guys,
>>
>> I have a form that has a long list of radio-bottons inside of it. The
>> radio-buttons are dynamically created via php and MySQL.
>>
>> Here is an example of one of the radio buttons:
>>
>> > ?>" value="0
At 9:28 PM +0200 3/11/11, Danny wrote:
Hi guys,
I have a form that has a long list of radio-bottons inside of it. The
radio-buttons are dynamically created via php and MySQL.
Here is an example of one of the radio buttons:
; ?>" value="0">
; ?>" value="1">
Now, when I submit this form to ano
On 11/03/2011 20:28, Danny wrote:
Hi guys,
I have a form that has a long list of radio-bottons inside of it. The
radio-buttons are dynamically created via php and MySQL.
Here is an example of one of the radio buttons:
"
value="0">
"
value="1">
Now, when I submit this form to another page fo
On Fri, 2011-03-11 at 21:28 +0200, Danny wrote:
> Hi guys,
>
> I have a form that has a long list of radio-bottons inside of it. The
> radio-buttons are dynamically created via php and MySQL.
>
> Here is an example of one of the radio buttons:
>
> "
> value="0">
> "
> value="1">
>
> Now, when
On Fri, Mar 11, 2011 at 14:28, Danny wrote:
[snip!]
>
> Now, when I submit this form to another page for processing, how would I
> "catch"
> the above radio-button's $_POST name since I do not know the name, only that
> it
> starts with "radio_" ?
One method is a foreach() loop.
$v) {
On Wed, 2010-12-01 at 20:18 +0400, Nadim Attari wrote:
> On 12/01/2010 07:18 PM, Jay Blanchard wrote:
> > [snip]
> >>> If I just put only this piece of code:
> >>>
> >>> >>> var_dump($_POST);
> >>> ?>
> >>>
> >>> i get nothing.
> > [/snip]
> >
> > Where are you putting this var_dump?
> >
> >
This thread is a really good example of how difficult it can be to
both explain and understand a problem. The original poster might want
to restate the question from scratch with a more explicit and complete
example.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http:/
[snip]
> Where are you putting this var_dump?
>
>
That's the only code on the page. Otherwise, the other codes - header(),
print, etc. are on the page.
[/snip]
var_dumping the POST on the same page from which the data originates
will not yield anything.
Page A - contains data to be posted.
Page
On 1 December 2010 14:50, Bundhoo M Nadim wrote:
> Hello,
>
> Can someone explain me what this piece of code basically does ?
>
> header("Expires: " . gmdate("D, d M Y H:i:s", time() + (0*60)) . "GMT");
> header("Pragma: no-cache");
> print "REDIRECT=http://www.domaine.com/page.php?";;
>
The function http_build_query() is turning your $_POST array into a
query string ($_GET), so the answer to this really depends where
you're trying to dump the array.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On 12/01/2010 07:18 PM, Jay Blanchard wrote:
[snip]
If I just put only this piece of code:
i get nothing.
[/snip]
Where are you putting this var_dump?
That's the only code on the page. Otherwise, the other codes - header(),
print, etc. are on the page.
nadim
--
PHP General Mailing L
On 1 December 2010 15:18, Marc Guay wrote:
>>> var_dump($_POST);
?>
>
> Where exactly are you putting this line?
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
If a script is ran via a url like ...
http://www.site.co
[snip]
>> If I just put only this piece of code:
>>
>> > var_dump($_POST);
>> ?>
>>
>> i get nothing.
[/snip]
Where are you putting this var_dump?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
>>> >> var_dump($_POST);
>>> ?>
Where exactly are you putting this line?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On 01/12/2010 19:01, Daniel P. Brown wrote:
On Wed, Dec 1, 2010 at 09:50, Bundhoo M Nadim wrote:
If I just put only this piece of code:
i get nothing. But the above codes is successfully redirecting me to
page.php with a properly constructed query string -> which means that $_POST
was never
On Wed, Dec 1, 2010 at 09:50, Bundhoo M Nadim wrote:
>
> If I just put only this piece of code:
>
> var_dump($_POST);
> ?>
>
> i get nothing. But the above codes is successfully redirecting me to
> page.php with a properly constructed query string -> which means that $_POST
> was never empty.
On 1 December 2010 14:50, Bundhoo M Nadim wrote:
> Hello,
>
> Can someone explain me what this piece of code basically does ?
>
> header("Expires: " . gmdate("D, d M Y H:i:s", time() + (0*60)) . "GMT");
> header("Pragma: no-cache");
> print "REDIRECT=http://www.domaine.com/page.php?";;
>
Op 2/24/10 11:18 AM, Ashley Sheridan schreef:
> On Wed, 2010-02-24 at 07:55 +, Jochem Maas wrote:
>
>> Op 2/22/10 10:49 PM, John Black schreef:
>>> On 02/22/2010 11:42 PM, Michael Shadle wrote:
The difference here is you can at least have some control over the data
and expect it in a
On Wed, 2010-02-24 at 12:34 +0100, Rene Veerman wrote:
> sry i gotta disagree.
>
> a function that queries $_POST/$_GET first and then $_COOKIE seems
> much wiser to me.
> it consolidates all logic in the script, and making that logic obvious
> by syntax, rather than relying on functionality bein
sry i gotta disagree.
a function that queries $_POST/$_GET first and then $_COOKIE seems
much wiser to me.
it consolidates all logic in the script, and making that logic obvious
by syntax, rather than relying on functionality being determined by
php.ini, which could well cause a new developer to l
On Wed, 2010-02-24 at 07:55 +, Jochem Maas wrote:
> Op 2/22/10 10:49 PM, John Black schreef:
> > On 02/22/2010 11:42 PM, Michael Shadle wrote:
> >> The difference here is you can at least have some control over the data
> >> and expect it in a certain fashion. Also the behavior of cookies vs.
Op 2/22/10 10:49 PM, John Black schreef:
> On 02/22/2010 11:42 PM, Michael Shadle wrote:
>> The difference here is you can at least have some control over the data
>> and expect it in a certain fashion. Also the behavior of cookies vs. get
>> vs. post are different (cookies have length and expirati
Op 2/23/10 10:27 AM, Ashley Sheridan schreef:
> On Tue, 2010-02-23 at 09:19 +, Richard wrote:
>
>> Hi,
>>
>> Well people better than me (how is that possible?!) have said that
>> $_REQUEST has the potential to open your app up to security
>> vulnerabilities, and that it should be avoided becau
At 11:07 PM +0100 2/22/10, John Black wrote:
On 02/22/2010 10:37 PM, Michael Shadle wrote:
On Mon, Feb 22, 2010 at 1:30 PM, David
Murphy wrote:
Richard,
The use of $_REQUEST it no more a security hole than $_GET or $_REQUEST,
they should ALL be treats as bad data until normalized and sanitized
From: Rene Veerman [mailto:rene7...@gmail.com]
> On Mon, Feb 22, 2010 at 9:39 PM, Slack-Moehrle
>>
>> Single quotes is best, correct to prevent sql injection?
>
> sql injection fixing is an evolving art, but you can start by pushing
> all variables that can be changed by end-users going into a da
On Tue, 2010-02-23 at 09:19 +, Richard wrote:
> Hi,
>
> Well people better than me (how is that possible?!) have said that
> $_REQUEST has the potential to open your app up to security
> vulnerabilities, and that it should be avoided because of that. Here's
> a post from Stephan Esser about i
Hi,
Well people better than me (how is that possible?!) have said that
$_REQUEST has the potential to open your app up to security
vulnerabilities, and that it should be avoided because of that. Here's
a post from Stephan Esser about it on the PHP-Internals list:
http://www.mail-archive.com/inter
On Mon, 2010-02-22 at 23:49 +0100, John Black wrote:
> On 02/22/2010 11:42 PM, Michael Shadle wrote:
> > The difference here is you can at least have some control over the data
> > and expect it in a certain fashion. Also the behavior of cookies vs. get
> > vs. post are different (cookies have len
On 02/22/2010 11:42 PM, Michael Shadle wrote:
The difference here is you can at least have some control over the data
and expect it in a certain fashion. Also the behavior of cookies vs. get
vs. post are different (cookies have length and expiration limits, get
has length limits, post has server
Op 2/22/10 8:39 PM, Slack-Moehrle schreef:
> Hi All,
>
> I have Forms that I submit for processing. I have seen examples of people
> using either $_POST or $_REQUEST.
>
> When would I choose one over the other?
use $_POST, $_REQUEST is normally an amalgam of GET, POST and COOKIE - as such
usin
The difference here is you can at least have some control over the
data and expect it in a certain fashion. Also the behavior of cookies
vs. get vs. post are different (cookies have length and expiration
limits, get has length limits, post has server confgured limits)
Like I said a properly
On Mon, Feb 22, 2010 at 22:37, Michael Shadle wrote:
> On Mon, Feb 22, 2010 at 1:30 PM, David Murphy wrote:
>> Richard,
>>
>>
>> The use of $_REQUEST it no more a security hole than $_GET or $_REQUEST,
>> they should ALL be treats as bad data until normalized and sanitized. The
>> claim that it
On 02/22/2010 11:17 PM, Michael Shadle wrote:
"Secure" might be the wrong term here. As you can easily change GET to
POST and vice-versa and send any cookies you like, this is why I tried
to revise my statement and quantify it better... in a properly coded
app it doesn't present much issue. Howev
On Mon, Feb 22, 2010 at 5:02 PM, Slack-Moehrle
wrote:
> John,
>
>>>Then if you use a MySQL database you would escape the string like this
>>>$tmp = mysql_real_escape_string($_REQUEST['yyy']);
>
>
>>>mysql_real_escape_string() protect from SQL injection by escaping your
>>>string according to what
On Mon, Feb 22, 2010 at 2:07 PM, John Black
wrote:
> And how is this more secure? I can create a cookie, send post or get on my
> client machine and send anything I want to the server. Just because you are
> getting a cookie does not mean that you created it :)
>
> So you might as well use reques
On 02/22/2010 10:37 PM, Michael Shadle wrote:
On Mon, Feb 22, 2010 at 1:30 PM, David Murphy wrote:
Richard,
The use of $_REQUEST it no more a security hole than $_GET or $_REQUEST,
they should ALL be treats as bad data until normalized and sanitized. The
claim that it opens a security hole is
John,
>>Then if you use a MySQL database you would escape the string like this
>>$tmp = mysql_real_escape_string($_REQUEST['yyy']);
>>mysql_real_escape_string() protect from SQL injection by escaping your
>>string according to what your charset requires.
Good point, I should be doing that. But
On Mon, Feb 22, 2010 at 1:30 PM, David Murphy wrote:
> Richard,
>
>
> The use of $_REQUEST it no more a security hole than $_GET or $_REQUEST,
> they should ALL be treats as bad data until normalized and sanitized. The
> claim that it opens a security hole is just false, that’s like saying PHP
$_REQUEST.
David Murphy
-Original Message-
From: richard.he...@gmail.com [mailto:richard.he...@gmail.com] On Behalf Of
Richard
Sent: Monday, February 22, 2010 3:03 PM
To: Joseph Thayne
Cc: Slack-Moehrle; php-general
Subject: Re: [PHP] $_POST vs $_REQUEST
Hi,
> I am not sure what
On Mon, Feb 22, 2010 at 12:55 PM, Joseph Thayne wrote:
> I am not sure what the security issues are you are referring to as the
> $_REQUEST superglobal contains both $_GET and $_POST values. Could you
> expound on that? Thanks.
$_REQUEST opens you up to POST/GET values overriding cookie values
> I have Forms that I submit for processing. I have seen examples of people
> using either $_POST or $_REQUEST.
>
Look at this example:
Now what do you thing $_REQUEST will return? You had better not even
think. Just use $_POST or $_GET as you _know_ what they will return.
Don't forget, the
Hi Slack-Moehrle
Slack-Moehrle wrote on 22/02/2010 21:39:
Hi All,
I have Forms that I submit for processing. I have seen examples of people using
either $_POST or $_REQUEST.
When would I choose one over the other?
$_REQUEST['test'] is true on both $_GET['test'] and $_POST['test']
I use it
Hi,
> I am not sure what the security issues are you are referring to as the
> $_REQUEST superglobal contains both $_GET and $_POST values. Could you
> expound on that? Thanks.
Not really, do a search.
--
Richard Heyes
HTML5 canvas graphing: RGraph - http://www.rgraph.net (updated 20th Februa
> i'd expect without quotes to query a define('j_orderValue','??')..
oh, and that, if not defined, defaults to the string 'j_orderValue'.
So while your $_POST[] with or without quotes will "do the same", use
single-quotes anyway because it's "the right thing to do" ;)
--
PHP General Mailing List
On 02/22/2010 09:39 PM, Slack-Moehrle wrote:
Hi All,
I have Forms that I submit for processing. I have seen examples of people using
either $_POST or $_REQUEST.
When would I choose one over the other?
When you don't care how you get the data use $_REQUEST.
$_REQUEST will contain $_GET,$_POST,$
On Mon, Feb 22, 2010 at 9:39 PM, Slack-Moehrle
wrote:
> Hi All,
>
> I have Forms that I submit for processing. I have seen examples of people
> using either $_POST or $_REQUEST.
>
> When would I choose one over the other?
I like to be specific and go for $_POST, but some people want
flexibility
Richard wrote:
It's a wise choice to go with $_POST, unless your form is a GET form,
in which case use $_GET. $_REQUEST has the potential to open your
script(s) up to security issues.
I am not sure what the security issues are you are referring to as the
$_REQUEST superglobal contains both
On Tue, Feb 23, 2010 at 2:39 AM, Slack-Moehrle
wrote:
> Hi All,
>
> I have Forms that I submit for processing. I have seen examples of people
> using either $_POST or $_REQUEST.
>
> When would I choose one over the other?
>
> Also, I see examples of these being used with and without the single qu
Hi,
> I have Forms that I submit for processing. I have seen examples of people
> using either $_POST or $_REQUEST.
>
> When would I choose one over the other?
It's a wise choice to go with $_POST, unless your form is a GET form,
in which case use $_GET. $_REQUEST has the potential to open your
On Thu, 2009-12-17 at 13:30 -0800, Steve wrote:
> On 12/17/2009 1:21 PM, gato chlr wrote:
> > Hi,
> > sorry for ask this again, but i really can't solve it.
> > It must be easy but i can't find the solution
> >
> > this is my code:
> > //form.php
> >
> > name :
> >
> >
> >
> > //and this is the
THANKS A LOT!!! to every one!!! . it works.
2009/12/17 Joseph Thayne
> Give your input a name. (i.e. name="myname")
>
> -Original Message-
> From: gato chlr [mailto:dany...@gmail.com]
> Sent: Thursday, December 17, 2009 3:22 PM
> To: php-general@lists.php.net
> Subject: [PHP] $_POST is
On 12/17/2009 1:21 PM, gato chlr wrote:
Hi,
sorry for ask this again, but i really can't solve it.
It must be easy but i can't find the solution
this is my code:
//form.php
name :
//and this is the mail.php
$name = $_POST["myname"];
var_dump($name);
and the result is:
NULL
i'm usi
Chris wrote:
> Luke wrote:
>> 2009/4/22 PJ
>>
>>> Could somebody explain to me the meaning of @ in $var =
>>> @$_POST['title'] ;
>>> where could I find a cheat sheet for those kinds of symbols or what are
>>> they called?
>>> Sorry for my ignorance, but maybe this will take the fog filter our of
>
On Thu, Apr 23, 2009 at 5:26 AM, PJ wrote:
> 9el wrote:
>> Rather than looking for cheatsheets you should read the ZCE
>> preparation guide book and PHP manual.
>>
>>
> That's a lame duck response. I'm not stupid enough to not search and try
> to find answers on G and in the manuals & tutorials. T
Luke wrote:
2009/4/22 PJ
Could somebody explain to me the meaning of @ in $var = @$_POST['title'] ;
where could I find a cheat sheet for those kinds of symbols or what are
they called?
Sorry for my ignorance, but maybe this will take the fog filter our of
my neurons. :-\
I believe placing an
9el wrote:
> Rather than looking for cheatsheets you should read the ZCE
> preparation guide book and PHP manual.
>
>
That's a lame duck response. I'm not stupid enough to not search and try
to find answers on G and in the manuals & tutorials. They are not always
obvious so I often rely on the g
Rather than looking for cheatsheets you should read the ZCE
preparation guide book and PHP manual.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
2009/4/22 PJ
> Could somebody explain to me the meaning of @ in $var = @$_POST['title'] ;
> where could I find a cheat sheet for those kinds of symbols or what are
> they called?
> Sorry for my ignorance, but maybe this will take the fog filter our of
> my neurons. :-\
>
> --
> unheralded genius:
Quoting "Daniel P. Brown" <[EMAIL PROTECTED]>:
On Wed, Dec 3, 2008 at 6:03 PM, Alex Kirk <[EMAIL PROTECTED]> wrote:
It works like a charm on a different machine with an essentially identical
config (it's a newer version of FreeBSD, but that's about it); however, it
never displays the contents
On Wed, Dec 3, 2008 at 6:03 PM, Alex Kirk <[EMAIL PROTECTED]> wrote:
>
> It works like a charm on a different machine with an essentially identical
> config (it's a newer version of FreeBSD, but that's about it); however, it
> never displays the contents of $_POST['testvar'] on the machine that
> s
[EMAIL PROTECTED] wrote:
There are httpd.conf settings to reject POST requests, but I don't think it
would behave like that...
But maybe it's a bit more complicated than what I've ever seen for httpd.conf
Could be mod_security getting in the way and killing some content.
--
Postgresql & php
There are httpd.conf settings to reject POST requests, but I don't think it
would behave like that...
But maybe it's a bit more complicated than what I've ever seen for httpd.conf
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
-Original Message-
From: Alex Kirk
I've got an Apache 2.2.3 server running PHP 5.2.6 on top of FreeBSD
6.2. It's worked quite well for over a year now. However, as of some
time last night, phpBB broke; upon investigation, I realized that the
problem was that $_POST was never getting
Hi Alain,
In short, you can't. It's the users computer that remembers what headers
it sent last time, and when you refresh, it WILL ask them to send those
headers again.
The way this is typically handled from a programming perspective is to
do all your processing on one page, and then jump a
[snip]
i have a PHP page with a form.
when user click on submit button, it sends form data to itself (so it
sends
data $_POST to itself).
i would like to access to header itself to reset those $_POST data to
avoid
(in case of F5 under windows system) to resend the same data serveral
time.
therefore
> On Jan 21, 2008 3:22 AM, nihilism machine <[EMAIL PROTECTED]> wrote:
> > I'm trying to create a function that will first take an array of
> > $_POSTs and give them key/value pairs like variables. For instance, if
> > i had $_POST['whatever'] = "whatever", that would be made into
> > $whatever = "
On Jan 21, 2008 3:22 AM, nihilism machine <[EMAIL PROTECTED]> wrote:
> I'm trying to create a function that will first take an array of
> $_POSTs and give them key/value pairs like variables. For instance, if
> i had $_POST['whatever'] = "whatever", that would be made into
> $whatever = "whatever",
On Jan 20, 2008 9:22 PM, nihilism machine <[EMAIL PROTECTED]> wrote:
> I'm trying to create a function that will first take an array of
> $_POSTs and give them key/value pairs like variables. For instance, if
> i had $_POST['whatever'] = "whatever", that would be made into
> $whatever = "whatever"
On 11/4/07, Mackatack <[EMAIL PROTECTED]> wrote:
>
> I have not defined any tags in my httpd.conf and by default
> apache should accept all request methods. I've stripped my apache config
> down to:
>
> Listen 80
> NameVirtualHost *:80
>
> ServerName my.server.com
> DocumentRoot
Jim Lucas schreef:
Mackatack wrote:
Nathan Nobbe schreef:
On 11/3/07, Mackatack <[EMAIL PROTECTED]> wrote:
Hey all!
Im trying to submit a very basic form to phpinfo():
readfile: ';
readfile("php://input")
phpinfo();
?>
When i use the button to submit the
Mackatack wrote:
Nathan Nobbe schreef:
On 11/3/07, Mackatack <[EMAIL PROTECTED]> wrote:
Hey all!
Im trying to submit a very basic form to phpinfo():
readfile: ';
readfile("php://input")
phpinfo();
?>
When i use the button to submit the form and it loads t
Nathan Nobbe schreef:
On 11/3/07, Mackatack <[EMAIL PROTECTED]> wrote:
Hey all!
Im trying to submit a very basic form to phpinfo():
readfile: ';
readfile("php://input")
phpinfo();
?>
When i use the button to submit the form and it loads the new page I get:
1 - 100 of 254 matches
Mail list logo
