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


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

PHP processing steps to apply to a URL to make it safe

Started byJames Harris <james.harris.1@gmail.com>
First post2016-02-17 09:37 +0000
Last post2016-03-22 05:23 -0700
Articles 6 on this page of 86 — 9 participants

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


Contents

  PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-17 09:37 +0000
    Re: PHP processing steps to apply to a URL to make it safe Arno Welzel <usenet@arnowelzel.de> - 2016-02-17 11:05 +0100
      Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-17 15:04 +0000
        Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 10:54 -0500
          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 Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 21:12 -0500
              Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-20 19:07 +0000
                Re: PHP processing steps to apply to a URL to make it safe Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-20 21:07 +0100
                  Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-20 20:35 +0000
                    Re: PHP processing steps to apply to a URL to make it safe Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-20 21:40 +0100
                      Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-20 21:02 +0000
                Re: PHP processing steps to apply to a URL to make it safe gordonb.lkcah@burditt.org (Gordon Burditt) - 2016-02-29 21:29 -0600
        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 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 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 Arno Welzel <usenet@arnowelzel.de> - 2016-02-18 08:05 +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
              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 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 Arno Welzel <usenet@arnowelzel.de> - 2016-02-18 08:02 +0100
          Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-20 19:29 +0000
            Re: PHP processing steps to apply to a URL to make it safe Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-20 21:37 +0100
              Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-20 21:37 +0000
                Re: PHP processing steps to apply to a URL to make it safe Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-21 15:02 +0100
                  Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-21 15:02 +0000
    Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 08:19 -0500
      Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> - 2016-02-17 14:43 +0100
        Re: PHP processing steps to apply to a URL to make it safe Arno Welzel <usenet@arnowelzel.de> - 2016-02-17 15:04 +0100
          Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> - 2016-02-17 15:17 +0100
            Re: PHP processing steps to apply to a URL to make it safe Arno Welzel <usenet@arnowelzel.de> - 2016-02-17 15:47 +0100
              Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> - 2016-02-17 15:57 +0100
                Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 10:57 -0500
                  Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> - 2016-02-17 17:10 +0100
                    Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 12:11 -0500
                      Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> - 2016-02-17 18:51 +0100
                        Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 12:55 -0500
                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 "R.Wieser" <address@not.available> - 2016-02-17 20:19 +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: 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 Arno Welzel <usenet@arnowelzel.de> - 2016-02-18 15:48 +0100
                          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: PHP processing steps to apply to a URL to make it safe Arno Welzel <usenet@arnowelzel.de> - 2016-02-18 17:00 +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: 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 "Christoph M. Becker" <cmbecker69@arcor.de> - 2016-02-17 16:38 +0100
                Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 10:56 -0500
                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 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 Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 09:56 -0500
              Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> - 2016-02-17 16:44 +0100
                Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 12:12 -0500
                  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 Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 09:55 -0500
          Re: PHP processing steps to apply to a URL to make it safe "R.Wieser" <address@not.available> - 2016-02-17 16:39 +0100
            Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 11:00 -0500
      Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-17 15:15 +0000
        Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-17 11:05 -0500
          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 Arno Welzel <usenet@arnowelzel.de> - 2016-02-17 19:14 +0100
          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 Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-17 23:36 +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 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 Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-18 22:03 +0100
          Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-20 19:38 +0000
            Re: PHP processing steps to apply to a URL to make it safe Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-20 21:17 +0100
              Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-20 20:56 +0000
                Re: PHP processing steps to apply to a URL to make it safe Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-20 23:48 +0100
                  Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-21 09:37 +0000
                    Re: PHP processing steps to apply to a URL to make it safe Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-21 14:42 +0100
                      Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-21 15:03 +0000
                        Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-21 14:09 -0500
                          Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-21 19:34 +0000
                            Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-21 14:49 -0500
                              Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-21 19:56 +0000
                                Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-21 20:29 -0500
                                  Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-22 07:30 +0000
                                    Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-22 08:13 -0500
                                      Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-22 15:01 +0000
                                        Re: PHP processing steps to apply to a URL to make it safe Jerry Stuckle <jstucklex@attglobal.net> - 2016-02-22 10:31 -0500
                            Re: PHP processing steps to apply to a URL to make it safe Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-02-22 00:10 +0100
                              Re: PHP processing steps to apply to a URL to make it safe James Harris <james.harris.1@gmail.com> - 2016-02-21 23:45 +0000
    Re: PHP processing steps to apply to a URL to make it safe pittendrigh <Sandy.Pittendrigh@gmail.com> - 2016-03-22 05:23 -0700

Page 5 of 5 — ← Prev page 1 2 3 4 [5]


#16587

FromJerry Stuckle <jstucklex@attglobal.net>
Date2016-02-22 08:13 -0500
Message-ID<naf1cf$e8a$1@jstuckle.eternal-september.org>
In reply to#16586
On 2/22/2016 2:30 AM, James Harris wrote:
> On 22/02/2016 01:29, Jerry Stuckle wrote:
>> On 2/21/2016 2:56 PM, James Harris wrote:
>>> On 21/02/2016 19:49, Jerry Stuckle wrote:
>>>> On 2/21/2016 2:34 PM, James Harris wrote:
>>>>> On 21/02/2016 19:09, Jerry Stuckle wrote:
>>>
>>> ...
>>>
>>>>>> One of the rare times I agree with Pointed Head.  This is a stupid
>>>>>> idea.
>>>>>
>>>>> OK, I'll bite. Why?
>>>
>>>> For all the reasons others and I have mentioned previously.  Read back
>>>> through the thread.
>>>
>>> I read every post. I wouldn't ask a question and then not read the
>>> replies.
> 
>> Obviously you didn't,
> 
> Yes, I did.
> 
>> or you didn't understand.
> 
> Well, it seems that someone didn't understand.
> 
>> There have been many
>> objections to what you're trying to do by several people.
> 
> As a matter of courtesy I have tried to respond to all the questions I
> was asked during the discussion as it went ahead. I don't remember
> anyone having remaining issues with my responses. I don't see what more
> a person can do to respond to your objections.
> 
> James
> 

You're hopeless.  I'm not going to waste any more time trying to help you.


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

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


#16588

FromJames Harris <james.harris.1@gmail.com>
Date2016-02-22 15:01 +0000
Message-ID<naf7no$7e8$1@dont-email.me>
In reply to#16587
On 22/02/2016 13:13, Jerry Stuckle wrote:
> On 2/22/2016 2:30 AM, James Harris wrote:
>> On 22/02/2016 01:29, Jerry Stuckle wrote:
>>> On 2/21/2016 2:56 PM, James Harris wrote:
>>>> On 21/02/2016 19:49, Jerry Stuckle wrote:
>>>>> On 2/21/2016 2:34 PM, James Harris wrote:
>>>>>> On 21/02/2016 19:09, Jerry Stuckle wrote:
>>>>
>>>> ...
>>>>
>>>>>>> One of the rare times I agree with Pointed Head.  This is a stupid
>>>>>>> idea.
>>>>>>
>>>>>> OK, I'll bite. Why?
>>>>
>>>>> For all the reasons others and I have mentioned previously.  Read back
>>>>> through the thread.
>>>>
>>>> I read every post. I wouldn't ask a question and then not read the
>>>> replies.
>>
>>> Obviously you didn't,
>>
>> Yes, I did.
>>
>>> or you didn't understand.
>>
>> Well, it seems that someone didn't understand.
>>
>>> There have been many
>>> objections to what you're trying to do by several people.
>>
>> As a matter of courtesy I have tried to respond to all the questions I
>> was asked during the discussion as it went ahead. I don't remember
>> anyone having remaining issues with my responses. I don't see what more
>> a person can do to respond to your objections.
>>
>> James
>>
>
> You're hopeless.  I'm not going to waste any more time trying to help you.

You're arrogant. A lot of your comments are not helpful but are about 
your opinions. I'm not going to waste any more time replying to your 
efforts to keep this thread going.

Not my style but that seems to be how you like to communicate.

James

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


#16589

FromJerry Stuckle <jstucklex@attglobal.net>
Date2016-02-22 10:31 -0500
Message-ID<naf9e1$du0$1@jstuckle.eternal-september.org>
In reply to#16588
On 2/22/2016 10:01 AM, James Harris wrote:
> On 22/02/2016 13:13, Jerry Stuckle wrote:
>> On 2/22/2016 2:30 AM, James Harris wrote:
>>> On 22/02/2016 01:29, Jerry Stuckle wrote:
>>>> On 2/21/2016 2:56 PM, James Harris wrote:
>>>>> On 21/02/2016 19:49, Jerry Stuckle wrote:
>>>>>> On 2/21/2016 2:34 PM, James Harris wrote:
>>>>>>> On 21/02/2016 19:09, Jerry Stuckle wrote:
>>>>>
>>>>> ...
>>>>>
>>>>>>>> One of the rare times I agree with Pointed Head.  This is a stupid
>>>>>>>> idea.
>>>>>>>
>>>>>>> OK, I'll bite. Why?
>>>>>
>>>>>> For all the reasons others and I have mentioned previously.  Read
>>>>>> back
>>>>>> through the thread.
>>>>>
>>>>> I read every post. I wouldn't ask a question and then not read the
>>>>> replies.
>>>
>>>> Obviously you didn't,
>>>
>>> Yes, I did.
>>>
>>>> or you didn't understand.
>>>
>>> Well, it seems that someone didn't understand.
>>>
>>>> There have been many
>>>> objections to what you're trying to do by several people.
>>>
>>> As a matter of courtesy I have tried to respond to all the questions I
>>> was asked during the discussion as it went ahead. I don't remember
>>> anyone having remaining issues with my responses. I don't see what more
>>> a person can do to respond to your objections.
>>>
>>> James
>>>
>>
>> You're hopeless.  I'm not going to waste any more time trying to help
>> you.
> 
> You're arrogant. A lot of your comments are not helpful but are about
> your opinions. I'm not going to waste any more time replying to your
> efforts to keep this thread going.
> 
> Not my style but that seems to be how you like to communicate.
> 
> James
> 

No, you just don't take advice from those who know more than you.  And
I'm including virtually everyone who has replied to you in this thread.
 You have taken none of their advice.

No, I'm not arrogant.  I just know it's a waste of time to try to teach
a pig to sing.

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

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


#16583

FromThomas 'PointedEars' Lahn <PointedEars@web.de>
Date2016-02-22 00:10 +0100
Message-ID<1852851.Fa4viQKSry@PointedEars.de>
In reply to#16580
James Harris wrote:

> On 21/02/2016 19:09, Jerry Stuckle wrote:
>> On 2/21/2016 10:03 AM, James Harris wrote:
>>> On 21/02/2016 13:42, Thomas 'PointedEars' Lahn wrote:
>>>> James Harris wrote:
>>>>> On 20/02/2016 22:48, Thomas 'PointedEars' Lahn wrote:
>>>>>> Because you would not rewrite *every* request to the same PHP
>>>>>> program, would you?
>>>>> Pretty much, yes. All of this is about processing such URLs in PHP
>>>>> code.
>>>> That is a stupid idea.
>>> No, it's the right idea for my application.
>> […]  This is a stupid idea.
> 
> OK, I'll bite. Why?

You want to run PHP on top of Web server software (Apache) and have PHP do 
what Web server software is supposed to do instead.

-- 
PointedEars
Zend Certified PHP Engineer 
<http://www.zend.com/en/yellow-pages/ZEND024953> | Twitter: @PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.

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


#16584

FromJames Harris <james.harris.1@gmail.com>
Date2016-02-21 23:45 +0000
Message-ID<nadi2j$cf5$1@dont-email.me>
In reply to#16583
On 21/02/2016 23:10, Thomas 'PointedEars' Lahn wrote:
> James Harris wrote:
>
>> On 21/02/2016 19:09, Jerry Stuckle wrote:
>>> On 2/21/2016 10:03 AM, James Harris wrote:
>>>> On 21/02/2016 13:42, Thomas 'PointedEars' Lahn wrote:
>>>>> James Harris wrote:
>>>>>> On 20/02/2016 22:48, Thomas 'PointedEars' Lahn wrote:
>>>>>>> Because you would not rewrite *every* request to the same PHP
>>>>>>> program, would you?
>>>>>> Pretty much, yes. All of this is about processing such URLs in PHP
>>>>>> code.
>>>>> That is a stupid idea.
>>>> No, it's the right idea for my application.
>>> […]  This is a stupid idea.
>>
>> OK, I'll bite. Why?
>
> You want to run PHP on top of Web server software (Apache) and have PHP do
> what Web server software is supposed to do instead.

Before I explain the details is this an objection to do with 
performance? If Apache and PHP could both carry out some or all of the 
work why exactly would you choose Apache over PHP?

To explain why PHP is needed (and I think this was one of the points we 
discussed), yes, the requests get directed to a PHP script but then the 
PHP script transforms the URL in ways that Apache cannot.

Specifically, given the URL http://example.com/B/C/D:

* B is the partition. The PHP script uses the partition name as a folder 
and looks in that folder for a configuration file. Each partition will 
be able to have a separate configuration.

* The configuration file tells the script how to transform the rest of 
the URL.

* The PHP script transforms the C/D part of the URL into a set of keys 
and uses those to locate a resource.

If nothing else, Apache cannot do this as the configuration file format 
will not be meaningful to Apache.

-- 
James

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


#16674

Frompittendrigh <Sandy.Pittendrigh@gmail.com>
Date2016-03-22 05:23 -0700
Message-ID<53af0f8a-2d00-4e7a-bcc1-0409df2e055a@googlegroups.com>
In reply to#16438
 
Haven't logged in for a decade.  Not surprised to find it's deja vu all over again.  

[toc] | [prev] | [standalone]


Page 5 of 5 — ← Prev page 1 2 3 4 [5]

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


csiph-web