On Sunday 29 January 2006 02:47, Nick Kew wrote:
> for (p = str; *p; ++p)
> if (*p == '+')
> *p = ' ' ;
that piece looks *exactly* like the code I quick'n'dirty inserted in order to
get around this (and not to stop working on my actual project)
longterm fix would be libapreq2 I
On Saturday 28 January 2006 22:32, Christian Parpart wrote:
> Hi all,
>
> I'm having a problem, mod_transform's GET argument parser is using
> ap_unescape_url() to decode the unescaped value of an GET query argument,
> wich works so far, however, firefox keeps adding '+' chars instead of %20
> to a
On Sunday 29 January 2006 00:59, Joe Schaefer wrote:
> Christian Parpart <[EMAIL PROTECTED]> writes:
> > On Saturday 28 January 2006 23:36, Dirk-Willem van Gulik wrote:
> >> On Sat, 28 Jan 2006, Christian Parpart wrote:
> >> > wich works so far, however, firefox keeps adding '+' chars instead of
>
Christian Parpart <[EMAIL PROTECTED]> writes:
> On Saturday 28 January 2006 23:36, Dirk-Willem van Gulik wrote:
>> On Sat, 28 Jan 2006, Christian Parpart wrote:
>> > wich works so far, however, firefox keeps adding '+' chars instead of %20
>> > to
>>
>> Which is perfectly OK/right - so we should r
On Saturday 28 January 2006 23:36, Dirk-Willem van Gulik wrote:
> On Sat, 28 Jan 2006, Christian Parpart wrote:
> > wich works so far, however, firefox keeps adding '+' chars instead of %20
> > to
>
> Which is perfectly OK/right - so we should recognize these and handlte
> htem correctly.
what exa
On Sat, 28 Jan 2006, Christian Parpart wrote:
> wich works so far, however, firefox keeps adding '+' chars instead of %20 to
Which is perfectly OK/right - so we should recognize these and handlte
htem correctly.
DW
Hi all,
I'm having a problem, mod_transform's GET argument parser is using
ap_unescape_url() to decode the unescaped value of an GET query argument,
wich works so far, however, firefox keeps adding '+' chars instead of %20 to
any kind of input/textarea/... form elements, though, not being able
