On Friday 13 March 2009, David Banning wrote:
> Yes - I have control of that - so I could filter out the problem in
> php. The only problem is that I don't know what I am filtering.
> If I know exactly what the erroneous characters are I could filter
> them - I have looked at the file in vi but th
Don't you have control over this web form??? That's the place
you should filter your input... The sooner you do the filtering
the better.
Anyway, you could also use an intermediate variable that replaces
all newlines with spaces.
# a="This
> is
> the
> input
> from the
> web server"
# b=`echo
David Banning wrote:
I have looked at the file in vi but the problematic characters are
invisible there.
The problematic character is the newline character, \n, ASCII 0xA.
And, yes vi is old but it's a few months now that it supports newlines
without problems;)
Nikos
__
David Banning wrote:
Nikos Vassiliadis wrote:
David Banning wrote:
Here is the php line that gives the error;
cat start_text | sed "s/--maintext--/$test/" > endtext
give error;
sed: 1: "s/--maintext--/ Comment ...": unescaped newline inside
substitute pattern
where $test contains customer
Nikos Vassiliadis wrote:
David Banning wrote:
Here is the php line that gives the error;
cat start_text | sed "s/--maintext--/$test/" > endtext
give error;
sed: 1: "s/--maintext--/ Comment ...": unescaped newline inside
substitute pattern
where $test contains customer input from a website
David Banning wrote:
Here is the php line that gives the error;
cat start_text | sed "s/--maintext--/$test/" > endtext
give error;
sed: 1: "s/--maintext--/ Comment ...": unescaped newline inside substitute
pattern
where $test contains customer input from a website form
There is something ab
On Thu, Mar 12, 2009 at 01:34:36PM -0400, David Banning wrote:
>
> Here is the php line that gives the error;
>
> cat start_text | sed "s/--maintext--/$test/" > endtext
>
> give error;
>
> sed: 1: "s/--maintext--/ Comment ...": unescaped newline inside substitute
> pattern
>
> where $test cont
> Well, it might be because "test" is a command line function.
It actually doesn't matter whether I use the word "test" or any other word as a
variable
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ques
On Thursday 12 March 2009 10:34:36 am David Banning wrote:
> Here is the php line that gives the error;
>
> cat start_text | sed "s/--maintext--/$test/" > endtext
>
> give error;
>
> sed: 1: "s/--maintext--/ Comment ...": unescaped newline inside substitute
> pattern
>
> where $test contains custom
Here is the php line that gives the error;
cat start_text | sed "s/--maintext--/$test/" > endtext
give error;
sed: 1: "s/--maintext--/ Comment ...": unescaped newline inside substitute
pattern
where $test contains customer input from a website form
There is something about the content of the
10 matches
Mail list logo
