Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
18446 articles (numbers 823 – 19616) — threaded view
| Advanced| Subject | Author | Date [asc] |
|---|---|---|
| Re: PHP processing steps to apply to a URL to make it safe | "R.Wieser" <address@not.available> | 2016-02-17 19:04 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Arno Welzel <usenet@arnowelzel.de> | 2016-02-17 19:06 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Arno Welzel <usenet@arnowelzel.de> | 2016-02-17 19:08 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Arno Welzel <usenet@arnowelzel.de> | 2016-02-17 19:14 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | "R.Wieser" <address@not.available> | 2016-02-17 20:19 +0100 |
| Re: Considering a new programming language after years with Visual Basic | wrong.address.1@gmail.com | 2016-02-17 11:38 -0800 |
| Re: Considering a new programming language after years with Visual Basic | wrong.address.1@gmail.com | 2016-02-17 11:40 -0800 |
| Re: Considering a new programming language after years with Visual Basic | wrong.address.1@gmail.com | 2016-02-17 11:44 -0800 |
| Re: Functions behaving badly: PHP str_split on an empty string | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-17 23:12 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-17 23:26 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-17 23:33 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-17 23:35 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-17 23:36 +0100 |
| Re: Considering a new programming language after years with Visual Basic | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-17 23:46 +0100 |
| Re: Considering a new programming language after years with Visual Basic | James Harris <james.harris.1@gmail.com> | 2016-02-18 00:03 +0000 |
| Re: Considering a new programming language after years with Visual Basic | James Harris <james.harris.1@gmail.com> | 2016-02-18 00:08 +0000 |
| Re: PHP processing steps to apply to a URL to make it safe | James Harris <james.harris.1@gmail.com> | 2016-02-18 00:19 +0000 |
| Re: PHP processing steps to apply to a URL to make it safe | James Harris <james.harris.1@gmail.com> | 2016-02-18 00:36 +0000 |
| Re: PHP processing steps to apply to a URL to make it safe | James Harris <james.harris.1@gmail.com> | 2016-02-18 01:09 +0000 |
| Re: PHP processing steps to apply to a URL to make it safe | James Harris <james.harris.1@gmail.com> | 2016-02-18 01:12 +0000 |
| Re: PHP processing steps to apply to a URL to make it safe | James Harris <james.harris.1@gmail.com> | 2016-02-18 01:18 +0000 |
| Re: PHP processing steps to apply to a URL to make it safe | Jerry Stuckle <jstucklex@attglobal.net> | 2016-02-17 21:12 -0500 |
| Re: PHP processing steps to apply to a URL to make it safe | Arno Welzel <usenet@arnowelzel.de> | 2016-02-18 08:02 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Arno Welzel <usenet@arnowelzel.de> | 2016-02-18 08:05 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Arno Welzel <usenet@arnowelzel.de> | 2016-02-18 08:18 +0100 |
| Re: Considering a new programming language after years with Visual Basic | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-18 08:26 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | "R.Wieser" <address@not.available> | 2016-02-18 09:20 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Tim Streater <timstreater@greenbee.net> | 2016-02-18 09:59 +0000 |
| Re: PHP processing steps to apply to a URL to make it safe | James Harris <james.harris.1@gmail.com> | 2016-02-18 10:29 +0000 |
| Re: PHP processing steps to apply to a URL to make it safe | Tim Streater <timstreater@greenbee.net> | 2016-02-18 11:36 +0000 |
| Any recommendations on using PHP to parse marked-up text? | James Harris <james.harris.1@gmail.com> | 2016-02-18 12:47 +0000 |
| Re: PHP processing steps to apply to a URL to make it safe | Arno Welzel <usenet@arnowelzel.de> | 2016-02-18 15:44 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Arno Welzel <usenet@arnowelzel.de> | 2016-02-18 15:48 +0100 |
| Re: Any recommendations on using PHP to parse marked-up text? | Arno Welzel <usenet@arnowelzel.de> | 2016-02-18 15:52 +0100 |
| Re: Any recommendations on using PHP to parse marked-up text? | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-02-18 14:56 +0000 |
| Re: PHP processing steps to apply to a URL to make it safe | "R.Wieser" <address@not.available> | 2016-02-18 16:25 +0100 |
| Re: Any recommendations on using PHP to parse marked-up text? | Jerry Stuckle <jstucklex@attglobal.net> | 2016-02-18 10:43 -0500 |
| Re: PHP processing steps to apply to a URL to make it safe | Jerry Stuckle <jstucklex@attglobal.net> | 2016-02-18 10:48 -0500 |
| Re: PHP processing steps to apply to a URL to make it safe | Arno Welzel <usenet@arnowelzel.de> | 2016-02-18 17:00 +0100 |
| Re: OT: wasted bytes | BartC <bc@freeuk.com> | 2016-02-18 19:12 +0000 |
| Re: OT: wasted bytes | Jerry Stuckle <jstucklex@attglobal.net> | 2016-02-18 15:25 -0500 |
| Re: OT: wasted bytes | Jerry Stuckle <jstucklex@attglobal.net> | 2016-02-18 15:27 -0500 |
| Re: PHP processing steps to apply to a URL to make it safe | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-18 21:47 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-18 21:48 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-18 22:03 +0100 |
| Re: Any recommendations on using PHP to parse marked-up text? | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-18 22:06 +0100 |
| Re: Any recommendations on using PHP to parse marked-up text? | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-18 22:14 +0100 |
| Re: PHP processing steps to apply to a URL to make it safe | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-18 22:26 +0100 |
| Re: Any recommendations on using PHP to parse marked-up text? | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-02-18 21:45 +0000 |
| Re: Any recommendations on using PHP to parse marked-up text? | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-02-18 23:09 +0100 |
« Previous 1 ... 61 62 63 64 65 ... 369 Next »
csiph-web