| 1 |
On 11/13/06, Thomas de Grenier de Latour <degrenier@×××××××××××.fr> wrote: |
| 2 |
> On Mon, 13 Nov 2006 10:02:25 +0100, Alexander Skwar |
| 3 |
> Though, an other reason for not accepting this patch is that some |
| 4 |
> websites may expect URL like this one, which relies on both encoded |
| 5 |
> and raw commas: http://foo.bar/param-1,param-2%2Cwith%2Ccommas,param-3 |
| 6 |
|
| 7 |
Huh? Both of the following requests are equivalent: |
| 8 |
|
| 9 |
http://foo.bar/param-1,param-2%2Cwith%2Ccommas,param-3 |
| 10 |
http://foo.bar/param-1%2Cparam-2%2Cwith%2Ccommas%2Cparam-3 |
| 11 |
|
| 12 |
This is because web servers are required to process the URL and |
| 13 |
unescape *any* '%' sequences. So in both cases the server 'backend' |
| 14 |
is going to see a request for: |
| 15 |
|
| 16 |
param-1,param-2,with,commas,param-3 |
| 17 |
|
| 18 |
-Richard |
| 19 |
-- |
| 20 |
gentoo-dev@g.o mailing list |
Archives