Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #9093 > unrolled thread

Rejecting Certain Non-ASCII Characters

Back to article view | Back to comp.lang.php

Contents

  Rejecting Certain Non-ASCII Characters Jim Higgins <ILikeMy@Privacy.bogus> - 2013-04-19 16:16 +0000
    Re: Rejecting Certain Non-ASCII Characters Lew Pitcher <lpitcher@teksavvy.com> - 2013-04-19 12:29 -0400
    Re: Rejecting Certain Non-ASCII Characters Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2013-04-19 09:30 -0700
      Re: Rejecting Certain Non-ASCII Characters Jim Higgins <ILikeMy@Privacy.bogus> - 2013-04-19 21:38 +0000
        Re: Rejecting Certain Non-ASCII Characters Jim Higgins <ILikeMy@Privacy.bogus> - 2013-04-19 22:11 +0000
    Re: Rejecting Certain Non-ASCII Characters Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-19 12:48 -0400
      Re: Rejecting Certain Non-ASCII Characters Jim Higgins <ILikeMy@Privacy.bogus> - 2013-04-19 21:46 +0000
        Re: Rejecting Certain Non-ASCII Characters Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-19 18:00 -0400
        Re: Rejecting Certain Non-ASCII Characters Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-20 01:23 +0200
    Re: Rejecting Certain Non-ASCII Characters Christoph Becker <cmbecker69@gmx.de> - 2013-04-19 19:38 +0200
      Re: Rejecting Certain Non-ASCII Characters Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-19 22:33 +0200
        Re: Rejecting Certain Non-ASCII Characters Christoph Becker <cmbecker69@gmx.de> - 2013-04-19 23:08 +0200
          Re: Rejecting Certain Non-ASCII Characters Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-20 01:12 +0200
            Re: Rejecting Certain Non-ASCII Characters Christoph Becker <cmbecker69@gmx.de> - 2013-04-22 13:25 +0200
              Re: Rejecting Certain Non-ASCII Characters Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-22 13:29 +0200
          Re: Rejecting Certain Non-ASCII Characters Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-20 14:08 +0200
            Re: Rejecting Certain Non-ASCII Characters Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-20 17:52 +0200
      Re: Rejecting Certain Non-ASCII Characters Jim Higgins <ILikeMy@Privacy.bogus> - 2013-04-19 22:06 +0000
        Re: Rejecting Certain Non-ASCII Characters Christoph Becker <cmbecker69@gmx.de> - 2013-04-20 00:26 +0200
          Re: Rejecting Certain Non-ASCII Characters Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-19 19:53 -0400
            Re: Rejecting Certain Non-ASCII Characters Christoph Becker <cmbecker69@gmx.de> - 2013-04-20 02:36 +0200
              Re: Rejecting Certain Non-ASCII Characters Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-19 20:58 -0400
                Re: Rejecting Certain Non-ASCII Characters Christoph Becker <cmbecker69@gmx.de> - 2013-04-20 03:34 +0200
    Re: Rejecting Certain Non-ASCII Characters Arno Welzel <usenet@arnowelzel.de> - 2013-04-19 22:19 +0200
    Re: Rejecting Certain Non-ASCII Characters "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2013-04-20 10:04 +0200
      Re: Rejecting Certain Non-ASCII Characters Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-20 14:15 +0200
        Re: Rejecting Certain Non-ASCII Characters "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2013-04-20 14:26 +0200
          Re: Rejecting Certain Non-ASCII Characters Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-20 14:34 +0200
          Re: Rejecting Certain Non-ASCII Characters Arno Welzel <usenet@arnowelzel.de> - 2013-04-20 14:41 +0200
            Re: Rejecting Certain Non-ASCII Characters Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-20 08:43 -0400
              Re: Rejecting Certain Non-ASCII Characters Arno Welzel <usenet@arnowelzel.de> - 2013-04-20 14:55 +0200
                Re: Rejecting Certain Non-ASCII Characters Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-20 09:04 -0400
                  Re: Rejecting Certain Non-ASCII Characters Arno Welzel <usenet@arnowelzel.de> - 2013-04-20 21:29 +0200
                    Re: Rejecting Certain Non-ASCII Characters Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-20 20:03 -0400
                      Re: Rejecting Certain Non-ASCII Characters Arno Welzel <usenet@arnowelzel.de> - 2013-04-21 06:51 +0200
                        Re: Rejecting Certain Non-ASCII Characters Arno Welzel <usenet@arnowelzel.de> - 2013-04-21 06:57 +0200
                          Re: Rejecting Certain Non-ASCII Characters Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-21 08:45 -0400
                            Re: Rejecting Certain Non-ASCII Characters Tim Streater <timstreater@greenbee.net> - 2013-04-21 15:09 +0100
                              Re: Rejecting Certain Non-ASCII Characters Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-21 10:29 -0400
                        Re: Rejecting Certain Non-ASCII Characters Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-21 08:44 -0400
                Re: Rejecting Certain Non-ASCII Characters The Natural Philosopher <tnp@invalid.invalid> - 2013-04-20 15:07 +0100
                  Re: Rejecting Certain Non-ASCII Characters Jerry Stuckle <jstucklex@attglobal.net> - 2013-04-20 20:06 -0400
            Re: Rejecting Certain Non-ASCII Characters "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2013-04-20 17:43 +0200
              Re: Rejecting Certain Non-ASCII Characters Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-20 18:01 +0200
                Re: Rejecting Certain Non-ASCII Characters "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2013-04-20 18:17 +0200
                  Address munging (was: Rejecting Certain Non-ASCII Characters) Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-20 18:23 +0200
              OT: Address munging (was: Re: Rejecting Certain Non-ASCII Characters) Arno Welzel <usenet@arnowelzel.de> - 2013-04-20 21:25 +0200
              Re: Rejecting Certain Non-ASCII Characters Denis McMahon <denismfmcmahon@gmail.com> - 2013-04-20 22:06 +0000
                Re: Rejecting Certain Non-ASCII Characters Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-22 14:10 +0200

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

#9128

Jerry Stuckle wrote:
> On 4/19/2013 6:26 PM, Christoph Becker wrote:
>> Jim Higgins wrote:
>>> On Fri, 19 Apr 2013 19:38:02 +0200, in
>>> <kkrvda$od5$1@speranza.aioe.org>, Christoph Becker <cmbecker69@gmx.de>
>>> wrote:
>>>
>>>> Jim Higgins wrote:
>>>>> I have a problem with people entering a slashed zero vs a standard
>>>>> ASCII zero into HTML forms intended to store data in a MySQL database.
>>>>
>>>> Is it really a slashed zero (U+0030 U+0338) they're entering, or do
>>>> they
>>>> enter some similar looking character such as the Danish Ø?  In the
>>>> former case you can simply replace the slashed zero with a standard
>>>> zero.  Assuming UTF-8 encoding:
>>>>
>>>>   $input = str_replace('\xCC\xB8', '', $input);
>>>
>>>
>>> It's usually 0x41 0x7E, but sometimes 0xD8.
>>
>> 0xD8 is Ø in ISO-8859-1 for example; I do not know which character
>> encoding represents the same or a similar character as 0x41 0x7E.
>> Anyway, ISTM you're missing to enforce a particular character encoding
>> for your document (see <http://www.w3.org/TR/html4/charset.html> for
>> HTML 4.01 documents).
>>
> 
> This is a recommendation only.  The browser is free to ignore it.  There
> is no way to force a browser to do anything in HTML.

The mentioned W3C recommendation also elaborates on the "charset"
parameter of the "Content-Type" header, which should be respected by all
user agents conforming to RFC 2616, if they have requested the URI with
a suitable "Accept-Charset" header.  Otherwise the PHP script may
respond with "406 Not acceptable" (and a body explaining the requirements).

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#9131

On 4/19/2013 8:36 PM, Christoph Becker wrote:
> Jerry Stuckle wrote:
>> On 4/19/2013 6:26 PM, Christoph Becker wrote:
>>> Jim Higgins wrote:
>>>> On Fri, 19 Apr 2013 19:38:02 +0200, in
>>>> <kkrvda$od5$1@speranza.aioe.org>, Christoph Becker <cmbecker69@gmx.de>
>>>> wrote:
>>>>
>>>>> Jim Higgins wrote:
>>>>>> I have a problem with people entering a slashed zero vs a standard
>>>>>> ASCII zero into HTML forms intended to store data in a MySQL database.
>>>>>
>>>>> Is it really a slashed zero (U+0030 U+0338) they're entering, or do
>>>>> they
>>>>> enter some similar looking character such as the Danish Ø?  In the
>>>>> former case you can simply replace the slashed zero with a standard
>>>>> zero.  Assuming UTF-8 encoding:
>>>>>
>>>>>    $input = str_replace('\xCC\xB8', '', $input);
>>>>
>>>>
>>>> It's usually 0x41 0x7E, but sometimes 0xD8.
>>>
>>> 0xD8 is Ø in ISO-8859-1 for example; I do not know which character
>>> encoding represents the same or a similar character as 0x41 0x7E.
>>> Anyway, ISTM you're missing to enforce a particular character encoding
>>> for your document (see <http://www.w3.org/TR/html4/charset.html> for
>>> HTML 4.01 documents).
>>>
>>
>> This is a recommendation only.  The browser is free to ignore it.  There
>> is no way to force a browser to do anything in HTML.
>
> The mentioned W3C recommendation also elaborates on the "charset"
> parameter of the "Content-Type" header, which should be respected by all
> user agents conforming to RFC 2616, if they have requested the URI with
> a suitable "Accept-Charset" header.  Otherwise the PHP script may
> respond with "406 Not acceptable" (and a body explaining the requirements).
>

SHOULD BE RESPECTED is the key phrase here.

All HTML is recommendations - including the charset.  Not all browsers 
follow all recommendations - or follow them the same way.

It does not guarantee you will not get non-ASCII characters, especially 
if the user is using a non-ASCII charset.

And PHP will not respond with a 406 unless the user sends a 406.  PHP 
has no idea what charset is set in the outgoing header.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#9135

Jerry Stuckle wrote:
> On 4/19/2013 8:36 PM, Christoph Becker wrote:
>> Jerry Stuckle wrote:
>>> On 4/19/2013 6:26 PM, Christoph Becker wrote:
>>>> Jim Higgins wrote:
>>>>> On Fri, 19 Apr 2013 19:38:02 +0200, in
>>>>> <kkrvda$od5$1@speranza.aioe.org>, Christoph Becker <cmbecker69@gmx.de>
>>>>> wrote:
>>>>>
>>>>>> Jim Higgins wrote:
>>>>>>> I have a problem with people entering a slashed zero vs a standard
>>>>>>> ASCII zero into HTML forms intended to store data in a MySQL
>>>>>>> database.
>>>>>>
>>>>>> Is it really a slashed zero (U+0030 U+0338) they're entering, or do
>>>>>> they
>>>>>> enter some similar looking character such as the Danish Ø?  In the
>>>>>> former case you can simply replace the slashed zero with a standard
>>>>>> zero.  Assuming UTF-8 encoding:
>>>>>>
>>>>>>    $input = str_replace('\xCC\xB8', '', $input);
>>>>>
>>>>>
>>>>> It's usually 0x41 0x7E, but sometimes 0xD8.
>>>>
>>>> 0xD8 is Ø in ISO-8859-1 for example; I do not know which character
>>>> encoding represents the same or a similar character as 0x41 0x7E.
>>>> Anyway, ISTM you're missing to enforce a particular character encoding
>>>> for your document (see <http://www.w3.org/TR/html4/charset.html> for
>>>> HTML 4.01 documents).
>>>>
>>>
>>> This is a recommendation only.  The browser is free to ignore it.  There
>>> is no way to force a browser to do anything in HTML.
>>
>> The mentioned W3C recommendation also elaborates on the "charset"
>> parameter of the "Content-Type" header, which should be respected by all
>> user agents conforming to RFC 2616, if they have requested the URI with
>> a suitable "Accept-Charset" header.  Otherwise the PHP script may
>> respond with "406 Not acceptable" (and a body explaining the
>> requirements).
>>
> 
> SHOULD BE RESPECTED is the key phrase here.
> 
> All HTML is recommendations - including the charset.  

A HTTP response header has nothing to do with HTML as you know.

>                                                       Not all browsers
> follow all recommendations - or follow them the same way.
>
> It does not guarantee you will not get non-ASCII characters, especially
> if the user is using a non-ASCII charset.

I didn't want to suggest to send

  Content-Type: text/html; charset=ASCII

I merely noticed, that a developer should be aware of charset issues and
do the best he can to /minimize/ unexpected or even arbitrary behavior.
 Letting the user agent /guess/ how the response is encoded
(respectively rely on the webserver's default), and how it should encode
the follow-up request is surely not the best solution.

> And PHP will not respond with a 406 unless the user sends a 406.  PHP
> has no idea what charset is set in the outgoing header.

Of course.  Therefore I've written "the PHP script ...".  The word
"script" was intended to imply, that the script author is responsible
for doing this.

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#9106

Jim Higgins, 2013-04-19 18:16:

[...]
> Is there a simple way in PHP to restrict input to the ASCII Character
> set, specifically hex 0x20 - 0x7E ?  Or a simple way to detect
> characters outside this range before committing them to the database?

Maybe ctype_print() may help:

<http://www.php.net/manual/en/function.ctype-print.php>



-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de

[toc] | [prev] | [next] | [standalone]

#9138

Am 19.04.2013 18:16, schrieb Jim Higgins:
> 
> I have a problem with people entering a slashed zero vs a standard
> ASCII zero into HTML forms intended to store data in a MySQL database.
> 
> Is there a simple way in PHP to restrict input to the ASCII Character
> set, specifically hex 0x20 - 0x7E ?  Or a simple way to detect
> characters outside this range before committing them to the database?
> 
> My mind says it should be easy to detect and that I should be able to
> do it myself, but for some reason I'm drawing a huge blank.
> 

I skipped the long discussion, it looks like having little to do with your question.

Input data has to be filtered, IN ANY CASE, plus properly escaped upon insertion into
the database.

For number input, do something like

	$val = sscanf($_POST[$key], '%d')

for signed numbers, or

	preg_match('#^[0-9]+$#', $_POST[$key])

for ASCII numbers. Other helpful functions are cast to integer, ctype_digit(), ...
	
/Str.

[toc] | [prev] | [next] | [standalone]

#9142

M. Strobel wrote:

> Am 19.04.2013 18:16, schrieb Jim Higgins:
>> I have a problem with people entering a slashed zero vs a standard
>> ASCII zero into HTML forms intended to store data in a MySQL database.
>> 
>> Is there a simple way in PHP to restrict input to the ASCII Character
>> set, specifically hex 0x20 - 0x7E ?  Or a simple way to detect
>> characters outside this range before committing them to the database?
>> 
>> My mind says it should be easy to detect and that I should be able to
>> do it myself, but for some reason I'm drawing a huge blank.
> 
> I skipped the long discussion, it looks like having little to do with your
> question.
> 
> Input data has to be filtered, IN ANY CASE, plus properly escaped upon
> insertion into the database.
> 
> For number input, do something like
> 
> $val = sscanf($_POST[$key], '%d')
> 
> for signed numbers, or
> 
> preg_match('#^[0-9]+$#', $_POST[$key])
> 
> for ASCII numbers. Other helpful functions are cast to integer,
> ctype_digit(), ...

Nobody said anything about numbers before, though, and with your From header 
field value you are *still* violating the Acceptable Use Policy of your 
Usenet service provider, uni-berlin.de.


PointedEars
-- 
var bugRiddenCrashPronePieceOfJunk = (
    navigator.userAgent.indexOf('MSIE 5') != -1
    && navigator.userAgent.indexOf('Mac') != -1
)  // Plone, register_function.js:16

[toc] | [prev] | [next] | [standalone]

#9144

Am 20.04.2013 14:15, schrieb Thomas 'PointedEars' Lahn:
> M. Strobel wrote:
> 
>> Am 19.04.2013 18:16, schrieb Jim Higgins:
>>> I have a problem with people entering a slashed zero vs a standard
>>> ASCII zero into HTML forms intended to store data in a MySQL database.
>>>
>>> Is there a simple way in PHP to restrict input to the ASCII Character
>>> set, specifically hex 0x20 - 0x7E ?  Or a simple way to detect
>>> characters outside this range before committing them to the database?
>>>
>>> My mind says it should be easy to detect and that I should be able to
>>> do it myself, but for some reason I'm drawing a huge blank.
>>
>> I skipped the long discussion, it looks like having little to do with your
>> question.
>>
>> Input data has to be filtered, IN ANY CASE, plus properly escaped upon
>> insertion into the database.
>>
>> For number input, do something like
>>
>> $val = sscanf($_POST[$key], '%d')
>>
>> for signed numbers, or
>>
>> preg_match('#^[0-9]+$#', $_POST[$key])
>>
>> for ASCII numbers. Other helpful functions are cast to integer,
>> ctype_digit(), ...
> 
> Nobody said anything about numbers before, though, and with your From header 
> field value you are *still* violating the Acceptable Use Policy of your 
> Usenet service provider, uni-berlin.de.
> 
> 
> PointedEars
> 
My code can be easily adapted. And then:

Wall Street Journal online

http://online.wsj.com/article/SB10001424052748704805204575594423931135084.html#

or Reuters

http://www.reuters.com/article/2011/03/17/us-eu-internet-privacy-idUSTRE72G48Z20110317

[toc] | [prev] | [next] | [standalone]

#9145

M. Strobel wrote:

> Am 20.04.2013 14:15, schrieb Thomas 'PointedEars' Lahn:
>> M. Strobel wrote:
>>> For number input, do something like
>>>
>>> $val = sscanf($_POST[$key], '%d')
>>>
>>> for signed numbers, or
>>>
>>> preg_match('#^[0-9]+$#', $_POST[$key])
>>>
>>> for ASCII numbers. Other helpful functions are cast to integer,
>>> ctype_digit(), ...
>> 
>> Nobody said anything about numbers before, though, and with your From
>> header field value you are *still* violating the Acceptable Use Policy of
>> your Usenet service provider, uni-berlin.de.
> 
> My code can be easily adapted.

Your code is a repetition of what was posted before (by me), and does not 
relate to the question at all, which was how to *reject* strings with 
certain characters.

> And then:
> [tl;dr]

You should tell that to your service provider after they canceled your 
account, so that they will at least have a good laugh.


PointedEars
-- 
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
  -- Richard Cornford, cljs, <f806at$ail$1$8300dec7@news.demon.co.uk>

[toc] | [prev] | [next] | [standalone]

#9147

M. Strobel, 2013-04-20 14:26:

[...]
> My code can be easily adapted. And then:
> 
> Wall Street Journal online
> 
> http://online.wsj.com/article/SB10001424052748704805204575594423931135084.html#
> 
> or Reuters
> 
> http://www.reuters.com/article/2011/03/17/us-eu-internet-privacy-idUSTRE72G48Z20110317

If you don't want to use a valid address, then use

<invalid@invalid.invalid>

Also see <http://www.individual.de/faq.php#5.3>

Did you get it now?


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de

[toc] | [prev] | [next] | [standalone]

#9150

On 4/20/2013 8:41 AM, Arno Welzel wrote:
> M. Strobel, 2013-04-20 14:26:
>
> [...]
>> My code can be easily adapted. And then:
>>
>> Wall Street Journal online
>>
>> http://online.wsj.com/article/SB10001424052748704805204575594423931135084.html#
>>
>> or Reuters
>>
>> http://www.reuters.com/article/2011/03/17/us-eu-internet-privacy-idUSTRE72G48Z20110317
>
> If you don't want to use a valid address, then use
>
> <invalid@invalid.invalid>
>
> Also see <http://www.individual.de/faq.php#5.3>
>
> Did you get it now?
>
>

What does this have to do with PHP, troll?

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#9151

Jerry Stuckle, 2013-04-20 14:43:

> On 4/20/2013 8:41 AM, Arno Welzel wrote:
>> M. Strobel, 2013-04-20 14:26:
>>
>> [...]
>>> My code can be easily adapted. And then:
>>>
>>> Wall Street Journal online
>>>
>>> http://online.wsj.com/article/SB10001424052748704805204575594423931135084.html#
>>>
>>> or Reuters
>>>
>>> http://www.reuters.com/article/2011/03/17/us-eu-internet-privacy-idUSTRE72G48Z20110317
>>
>> If you don't want to use a valid address, then use
>>
>> <invalid@invalid.invalid>
>>
>> Also see <http://www.individual.de/faq.php#5.3>
>>
>> Did you get it now?
>>
>>
> 
> What does this have to do with PHP, troll?

You forgot to ask this M. Strobel and Thomas Lahn as well...


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de

[toc] | [prev] | [next] | [standalone]

#9152

On 4/20/2013 8:55 AM, Arno Welzel wrote:
> Jerry Stuckle, 2013-04-20 14:43:
>
>> On 4/20/2013 8:41 AM, Arno Welzel wrote:
>>> M. Strobel, 2013-04-20 14:26:
>>>
>>> [...]
>>>> My code can be easily adapted. And then:
>>>>
>>>> Wall Street Journal online
>>>>
>>>> http://online.wsj.com/article/SB10001424052748704805204575594423931135084.html#
>>>>
>>>> or Reuters
>>>>
>>>> http://www.reuters.com/article/2011/03/17/us-eu-internet-privacy-idUSTRE72G48Z20110317
>>>
>>> If you don't want to use a valid address, then use
>>>
>>> <invalid@invalid.invalid>
>>>
>>> Also see <http://www.individual.de/faq.php#5.3>
>>>
>>> Did you get it now?
>>>
>>>
>>
>> What does this have to do with PHP, troll?
>
> You forgot to ask this M. Strobel and Thomas Lahn as well...
>
>

Answer the question, troll.  What does this have to do with PHP?

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#9161

Jerry Stuckle, 2013-04-20 15:04:

> On 4/20/2013 8:55 AM, Arno Welzel wrote:
>> Jerry Stuckle, 2013-04-20 14:43:
>>
>>> On 4/20/2013 8:41 AM, Arno Welzel wrote:
>>>> M. Strobel, 2013-04-20 14:26:
>>>>
>>>> [...]
>>>>> My code can be easily adapted. And then:
>>>>>
>>>>> Wall Street Journal online
>>>>>
>>>>> http://online.wsj.com/article/SB10001424052748704805204575594423931135084.html#
>>>>>
>>>>> or Reuters
>>>>>
>>>>> http://www.reuters.com/article/2011/03/17/us-eu-internet-privacy-idUSTRE72G48Z20110317
>>>>
>>>> If you don't want to use a valid address, then use
>>>>
>>>> <invalid@invalid.invalid>
>>>>
>>>> Also see <http://www.individual.de/faq.php#5.3>
>>>>
>>>> Did you get it now?
>>>>
>>>>
>>>
>>> What does this have to do with PHP, troll?
>>
>> You forgot to ask this M. Strobel and Thomas Lahn as well...
>>
>>
> 
> Answer the question, troll.  What does this have to do with PHP?


<http://www.individual.de/faq.php#5.3> is an example for the use of PHP
(PHP 5.3.3 to be precise) ;-)


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de

[toc] | [prev] | [next] | [standalone]

#9165

On 4/20/2013 3:29 PM, Arno Welzel wrote:
> Jerry Stuckle, 2013-04-20 15:04:
>
>> On 4/20/2013 8:55 AM, Arno Welzel wrote:
>>> Jerry Stuckle, 2013-04-20 14:43:
>>>
>>>> On 4/20/2013 8:41 AM, Arno Welzel wrote:
>>>>> M. Strobel, 2013-04-20 14:26:
>>>>>
>>>>> [...]
>>>>>> My code can be easily adapted. And then:
>>>>>>
>>>>>> Wall Street Journal online
>>>>>>
>>>>>> http://online.wsj.com/article/SB10001424052748704805204575594423931135084.html#
>>>>>>
>>>>>> or Reuters
>>>>>>
>>>>>> http://www.reuters.com/article/2011/03/17/us-eu-internet-privacy-idUSTRE72G48Z20110317
>>>>>
>>>>> If you don't want to use a valid address, then use
>>>>>
>>>>> <invalid@invalid.invalid>
>>>>>
>>>>> Also see <http://www.individual.de/faq.php#5.3>
>>>>>
>>>>> Did you get it now?
>>>>>
>>>>>
>>>>
>>>> What does this have to do with PHP, troll?
>>>
>>> You forgot to ask this M. Strobel and Thomas Lahn as well...
>>>
>>>
>>
>> Answer the question, troll.  What does this have to do with PHP?
>
>
> <http://www.individual.de/faq.php#5.3> is an example for the use of PHP
> (PHP 5.3.3 to be precise) ;-)
>
>

ROFLMAO, troll.  Did you even read it?  (Unlike you, I do understand 
German, although I'm a bit rusty since it has been over 40 years...)

You can't even answer the question.  How like a troll!

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#9167

Jerry Stuckle, 2013-04-21 02:03:

> On 4/20/2013 3:29 PM, Arno Welzel wrote:
>> Jerry Stuckle, 2013-04-20 15:04:
>>
>>> On 4/20/2013 8:55 AM, Arno Welzel wrote:
>>>> Jerry Stuckle, 2013-04-20 14:43:
>>>>
>>>>> On 4/20/2013 8:41 AM, Arno Welzel wrote:
>>>>>> M. Strobel, 2013-04-20 14:26:
>>>>>>
>>>>>> [...]
>>>>>>> My code can be easily adapted. And then:
>>>>>>>
>>>>>>> Wall Street Journal online
>>>>>>>
>>>>>>> http://online.wsj.com/article/SB10001424052748704805204575594423931135084.html#
>>>>>>>
>>>>>>> or Reuters
>>>>>>>
>>>>>>> http://www.reuters.com/article/2011/03/17/us-eu-internet-privacy-idUSTRE72G48Z20110317
>>>>>>
>>>>>> If you don't want to use a valid address, then use
>>>>>>
>>>>>> <invalid@invalid.invalid>
>>>>>>
>>>>>> Also see <http://www.individual.de/faq.php#5.3>
>>>>>>
>>>>>> Did you get it now?
>>>>>>
>>>>>>
>>>>>
>>>>> What does this have to do with PHP, troll?
>>>>
>>>> You forgot to ask this M. Strobel and Thomas Lahn as well...
>>>>
>>>>
>>>
>>> Answer the question, troll.  What does this have to do with PHP?
>>
>>
>> <http://www.individual.de/faq.php#5.3> is an example for the use of PHP
>> (PHP 5.3.3 to be precise) ;-)
>>
>>
> 
> ROFLMAO, troll.  Did you even read it?  (Unlike you, I do understand 
> German, although I'm a bit rusty since it has been over 40 years...)
> 
> You can't even answer the question.  How like a troll!

But you even don't understand a joke... but i'm not surprised.


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de

[toc] | [prev] | [next] | [standalone]

#9168

Arno Welzel, 2013-04-21 06:51:

> Jerry Stuckle, 2013-04-21 02:03:
> 
>> On 4/20/2013 3:29 PM, Arno Welzel wrote:
>>> Jerry Stuckle, 2013-04-20 15:04:
>>>
>>>> On 4/20/2013 8:55 AM, Arno Welzel wrote:
>>>>> Jerry Stuckle, 2013-04-20 14:43:
>>>>>
>>>>>> On 4/20/2013 8:41 AM, Arno Welzel wrote:
>>>>>>> M. Strobel, 2013-04-20 14:26:
>>>>>>>
>>>>>>> [...]
>>>>>>>> My code can be easily adapted. And then:
>>>>>>>>
>>>>>>>> Wall Street Journal online
>>>>>>>>
>>>>>>>> http://online.wsj.com/article/SB10001424052748704805204575594423931135084.html#
>>>>>>>>
>>>>>>>> or Reuters
>>>>>>>>
>>>>>>>> http://www.reuters.com/article/2011/03/17/us-eu-internet-privacy-idUSTRE72G48Z20110317
>>>>>>>
>>>>>>> If you don't want to use a valid address, then use
>>>>>>>
>>>>>>> <invalid@invalid.invalid>
>>>>>>>
>>>>>>> Also see <http://www.individual.de/faq.php#5.3>
>>>>>>>
>>>>>>> Did you get it now?
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> What does this have to do with PHP, troll?
>>>>>
>>>>> You forgot to ask this M. Strobel and Thomas Lahn as well...
>>>>>
>>>>>
>>>>
>>>> Answer the question, troll.  What does this have to do with PHP?
>>>
>>>
>>> <http://www.individual.de/faq.php#5.3> is an example for the use of PHP
>>> (PHP 5.3.3 to be precise) ;-)
>>>
>>>
>>
>> ROFLMAO, troll.  Did you even read it?  (Unlike you, I do understand 
>> German, although I'm a bit rusty since it has been over 40 years...)
>>
>> You can't even answer the question.  How like a troll!
> 
> But you even don't understand a joke... but i'm not surprised.

PS: To help you a, if you still don't get it:

GET /faq.php HTTP/1.1
Host: www.individual.de

...

HTTP/1.1 200 OK
Date: Sun, 21 Apr 2013 04:56:22 GMT
Server: Apache/2.2.16 (Debian)
X-Powered-By: PHP/5.3.3-7+squeeze15


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de

[toc] | [prev] | [next] | [standalone]

#9170

On 4/21/2013 12:57 AM, Arno Welzel wrote:
> Arno Welzel, 2013-04-21 06:51:
>
>> Jerry Stuckle, 2013-04-21 02:03:
>>
>>> On 4/20/2013 3:29 PM, Arno Welzel wrote:
>>>> Jerry Stuckle, 2013-04-20 15:04:
>>>>
>>>>> On 4/20/2013 8:55 AM, Arno Welzel wrote:
>>>>>> Jerry Stuckle, 2013-04-20 14:43:
>>>>>>
>>>>>>> On 4/20/2013 8:41 AM, Arno Welzel wrote:
>>>>>>>> M. Strobel, 2013-04-20 14:26:
>>>>>>>>
>>>>>>>> [...]
>>>>>>>>> My code can be easily adapted. And then:
>>>>>>>>>
>>>>>>>>> Wall Street Journal online
>>>>>>>>>
>>>>>>>>> http://online.wsj.com/article/SB10001424052748704805204575594423931135084.html#
>>>>>>>>>
>>>>>>>>> or Reuters
>>>>>>>>>
>>>>>>>>> http://www.reuters.com/article/2011/03/17/us-eu-internet-privacy-idUSTRE72G48Z20110317
>>>>>>>>
>>>>>>>> If you don't want to use a valid address, then use
>>>>>>>>
>>>>>>>> <invalid@invalid.invalid>
>>>>>>>>
>>>>>>>> Also see <http://www.individual.de/faq.php#5.3>
>>>>>>>>
>>>>>>>> Did you get it now?
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> What does this have to do with PHP, troll?
>>>>>>
>>>>>> You forgot to ask this M. Strobel and Thomas Lahn as well...
>>>>>>
>>>>>>
>>>>>
>>>>> Answer the question, troll.  What does this have to do with PHP?
>>>>
>>>>
>>>> <http://www.individual.de/faq.php#5.3> is an example for the use of PHP
>>>> (PHP 5.3.3 to be precise) ;-)
>>>>
>>>>
>>>
>>> ROFLMAO, troll.  Did you even read it?  (Unlike you, I do understand
>>> German, although I'm a bit rusty since it has been over 40 years...)
>>>
>>> You can't even answer the question.  How like a troll!
>>
>> But you even don't understand a joke... but i'm not surprised.
>
> PS: To help you a, if you still don't get it:
>
> GET /faq.php HTTP/1.1
> Host: www.individual.de
>
> ...
>
> HTTP/1.1 200 OK
> Date: Sun, 21 Apr 2013 04:56:22 GMT
> Server: Apache/2.2.16 (Debian)
> X-Powered-By: PHP/5.3.3-7+squeeze15
>
>

Answer the question, troll!

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#9171

In article <kl0mrd$98a$2@dont-email.me>,
 Jerry Stuckle <jstucklex@attglobal.net> wrote:

> On 4/21/2013 12:57 AM, Arno Welzel wrote:

> > PS: To help you a, if you still don't get it:
> >
> > GET /faq.php HTTP/1.1
> > Host: www.individual.de
> >
> > ...
> >
> > HTTP/1.1 200 OK
> > Date: Sun, 21 Apr 2013 04:56:22 GMT
> > Server: Apache/2.2.16 (Debian)
> > X-Powered-By: PHP/5.3.3-7+squeeze15

> Answer the question, troll!

Christ on a bicycle, Jerry. Is everyone a troll in your book now? Get a 
grip, why don't you.

-- 
Tim

"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted"  --  Bill of Rights 1689

[toc] | [prev] | [next] | [standalone]

#9172

On 4/21/2013 10:09 AM, Tim Streater wrote:
> In article <kl0mrd$98a$2@dont-email.me>,
> Jerry Stuckle <jstucklex@attglobal.net> wrote:
>
>> On 4/21/2013 12:57 AM, Arno Welzel wrote:
>
>> > PS: To help you a, if you still don't get it:
>> >
>> > GET /faq.php HTTP/1.1
>> > Host: www.individual.de
>> >
>> > ...
>> >
>> > HTTP/1.1 200 OK
>> > Date: Sun, 21 Apr 2013 04:56:22 GMT
>> > Server: Apache/2.2.16 (Debian)
>> > X-Powered-By: PHP/5.3.3-7+squeeze15
>
>> Answer the question, troll!
>
> Christ on a bicycle, Jerry. Is everyone a troll in your book now? Get a
> grip, why don't you.
>

Just the trolls, Timmy.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#9169

On 4/21/2013 12:51 AM, Arno Welzel wrote:
> Jerry Stuckle, 2013-04-21 02:03:
>
>> On 4/20/2013 3:29 PM, Arno Welzel wrote:
>>> Jerry Stuckle, 2013-04-20 15:04:
>>>
>>>> On 4/20/2013 8:55 AM, Arno Welzel wrote:
>>>>> Jerry Stuckle, 2013-04-20 14:43:
>>>>>
>>>>>> On 4/20/2013 8:41 AM, Arno Welzel wrote:
>>>>>>> M. Strobel, 2013-04-20 14:26:
>>>>>>>
>>>>>>> [...]
>>>>>>>> My code can be easily adapted. And then:
>>>>>>>>
>>>>>>>> Wall Street Journal online
>>>>>>>>
>>>>>>>> http://online.wsj.com/article/SB10001424052748704805204575594423931135084.html#
>>>>>>>>
>>>>>>>> or Reuters
>>>>>>>>
>>>>>>>> http://www.reuters.com/article/2011/03/17/us-eu-internet-privacy-idUSTRE72G48Z20110317
>>>>>>>
>>>>>>> If you don't want to use a valid address, then use
>>>>>>>
>>>>>>> <invalid@invalid.invalid>
>>>>>>>
>>>>>>> Also see <http://www.individual.de/faq.php#5.3>
>>>>>>>
>>>>>>> Did you get it now?
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> What does this have to do with PHP, troll?
>>>>>
>>>>> You forgot to ask this M. Strobel and Thomas Lahn as well...
>>>>>
>>>>>
>>>>
>>>> Answer the question, troll.  What does this have to do with PHP?
>>>
>>>
>>> <http://www.individual.de/faq.php#5.3> is an example for the use of PHP
>>> (PHP 5.3.3 to be precise) ;-)
>>>
>>>
>>
>> ROFLMAO, troll.  Did you even read it?  (Unlike you, I do understand
>> German, although I'm a bit rusty since it has been over 40 years...)
>>
>> You can't even answer the question.  How like a troll!
>
> But you even don't understand a joke... but i'm not surprised.
>
>

Answer the question, troll!

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | comp.lang.php

csiph-web