On Tue, February 6, 2007 4:01 pm, Roman Neuhauser wrote:
> # [EMAIL PROTECTED] / 2007-02-05 18:09:21 -0600:
>> GET args can be truncated at some number, if the server does not
>> want
>> to allow longer args. I believe the minimum compliant limit is 1024
>> bytes.
I may well have been remembering
# [EMAIL PROTECTED] / 2007-02-05 18:09:21 -0600:
> GET args can be truncated at some number, if the server does not want
> to allow longer args. I believe the minimum compliant limit is 1024
> bytes.
Since you asked for a reference in the other post: HTTP/1.1 tries to be
as general as possible, a
On Mon, February 5, 2007 2:36 pm, Oscar Gosdinski wrote:
> When you send GET all the parameters are sent in the HTTP header and
> this header has a limited length. If you want to send large parameters
> in a form you have to use POST which send this data on the HTTP body
> and it has no limit.
Las
On Mon, February 5, 2007 2:11 pm, [EMAIL PROTECTED] wrote:
> If you're really intent on setting up a PHP powered web page to test
> SQL statements, I might recommend using a web form either using input
> type=text or textarea form elements and a POST method instead of GET.
I belive the minimum com
GET args can be truncated at some number, if the server does not want
to allow longer args. I believe the minimum compliant limit is 1024
bytes.
You also REALLY ought to be using http://php.net/urlencode on the GET
args.
And if you are spitting that URL out to a browser, you should then use
http
At 3:11 PM -0500 2/5/07, <[EMAIL PROTECTED]> wrote:
That seems to be cutting off around 900 characters. That's a lot to
put into a URL.
That figure varies. I did some testing on one of my servers and the
cut off was somewhere around 7000 characters. However, I don't
recommend the practice.
When you send GET all the parameters are sent in the HTTP header and
this header has a limited length. If you want to send large parameters
in a form you have to use POST which send this data on the HTTP body
and it has no limit.
On 2/5/07, Ramon <[EMAIL PROTECTED]> wrote:
Hi all,
I've written
Ramon-15 wrote:
>
> Hi all,
>
> I've written a php script, called test.php, consisting of the following
> statements:
>
> error_reporting(E_ALL);
> $query = $_GET['sql'];
> echo $query;
> ?>
> Using the script with 'small' values for the parameter sql works fine.
> Although, using the scri
I'll let everyone else do the "why the hell are you doing this? security blah
blah! bad practice blah blah!" type stuff.. I'm sure there will be plenty.
One reason this may be happening is, depending on your browser, there's a limit
to the number of characters you can have in a URL.
That seem
Ramon wrote:
I've written a php script, called test.php, consisting of the following
statements:
Using the script with 'small' values for the parameter sql works fine.
Although, using the script with the sql query as specified below
I do not understand why the value of the sql parameter is
Hi all,
I've written a php script, called test.php, consisting of the following
statements:
Using the script with 'small' values for the parameter sql works fine.
Although, using the script with the sql query as specified below
http://localhost/test.php?sql="SELECT orders_id, customers_id,
c
11 matches
Mail list logo
