get parameters

Anon

When I submit my document, I would like to get the value of a field. I would like to get "foo" for example.

But, in my new document, I get my field has a value like " foo" where the space is, I think, a "\n" car.

I don't have this problem with my LAN Apache server, but just with my provider Apache server.

Why have I this problem ?? And how can I solve it ??

mastah

That is indeed a weird problem! Anyway here is a possible solution :

ltrim (PHP 3, PHP 4 )
Strip whitespace from the beginning of a string
string ltrim (string str)
This function strips whitespace from the start of a string and returns the stripped string. The whitespace characters it
currently strips are: "\n", "\r", "\t", "\v", "\0", and a plain space.
See also chop(), rtrim(), and trim().

-Paulo

Anon

Yes, it's a partial solution.

But, I already have 10 000 lines of PHP, and it's a work to verify all parameters.

There's a problem with the provider's Apache server, don't you think ??

mastah

Well, none i can remember of.
Those values come from a form ? are you sure you don't have something like :

-Paulo

Anon

Yes, those values come from a form like this :

<INPUT TYPE="HIDDEN" NAME="High_Status">
or

with $firm can be empty.

For you, where is the problem ?

mastah

What is the version of Apache and PHP that you're using ?

Is it the PHP4.0.4pl1-3 ?

-Paulo

Anon

Hello!
I've been trying to solve the same problem with a similar script. It seams that the submition of the form, adds an "\r" (code 13)to position 0 of the var. It's wird that this happens, could this be some kind of PHP bug?

Anon

It's the PHP4.0.4pl1 and the Apache1.3.14.

Anon

I hope not

Anon

Hi,

Found the problem!

You should be using RedHat RPMS as we were, and we still are, but I had to pull out the source RPM and fiddle a little so I could find the problem.

The problem resides in a patch, php-4.0.4pl1-quotes.patch to be more specific. RedHat's source RPM is compiled after this patch is applied to PHP's source tree, then, resulting in this faulty operation.

A simple and fast solution, change the spec file so this patch isn't applied. I'm still trying to figure out where the problem is, debugging the source code after the patch.

Hope this could help.

Anon

IT'S PERFECT.

Thank you. You save my life ;-))