Problem with links with form data

wrote:
> Less than 1% of my users say they can not open links like this:
>
> index.php?variable=value&variable2=value2
>
> Is anyone aware of some firewall/security setting that would prevent
> people from clicking on such types of links?
>

Hi,

In short: No, should work.
That is if the value1 and value2 are properly URL-encoded.

However, if memory serves me well, the right way to use & is & in URLs.
(I never do that for esthetical reasons and never had any trouble. )

Can you isolate the 1%?
Do they all use the same OS or browser maybe?
Or are they all from one office or something like that?

Regards,
Erwin Moller
 >> Stay informed about: Problem with links with form data 

On Wed, 01 Aug 2007 16:26:09 +0200, wrote:
> Less than 1% of my users say they can not open links like this:
>
> index.php?variable=value&variable2=value2

Just a wild stab in the dark: are the 7 encoded (like &)?

> Is anyone aware of some firewall/security setting that would prevent
> people from clicking on such types of links?

Nope, not here, posting sometimes, but simple GET string filtering I have
not yet discovered. Can't they get the link at all or do you see something
in the server logs, and if so, what?
--
Rik Wasmus
 >> Stay informed about: Problem with links with form data 

On Wed, 01 Aug 2007 16:36:55 +0200, Erwin Moller
wrote:

> wrote:
>> Less than 1% of my users say they can not open links like this:
>> index.php?variable=value&variable2=value2
>> Is anyone aware of some firewall/security setting that would prevent
>> people from clicking on such types of links?
>>
>
> In short: No, should work.
> That is if the value1 and value2 are properly URL-encoded.

If the link is 'clicked', it should be urlencoded automatically me
thinks...

> However, if memory serves me well, the right way to use & is & in
> URLs.
> (I never do that for esthetical reasons and never had any trouble. )

Well, not in URL's, but if the URL is an HTML attribute then yes.
--
Rik Wasmus
 >> Stay informed about: Problem with links with form data 

On Wed, 01 Aug 2007 16:40:34 +0200, Rik wrote:

> On Wed, 01 Aug 2007 16:36:55 +0200, Erwin Moller
> wrote:
>
>> wrote:
>>> Less than 1% of my users say they can not open links like this:
>>> index.php?variable=value&variable2=value2
>>> Is anyone aware of some firewall/security setting that would prevent
>>> people from clicking on such types of links?
>>>
>>
>> In short: No, should work.
>> That is if the value1 and value2 are properly URL-encoded.
>
> If the link is 'clicked', it should be urlencoded automatically me
> thinks...

Me thinks wrong, why the hell did I say that?

If a form is posted using a GET, it should be encoded automatically, not
in a straight URL.

So, in short:

$link = htmlspecialchars(<path>).'?'.urlencode(<query_string>);
--
Rik Wasmus
 >> Stay informed about: Problem with links with form data 

On Wed, 01 Aug 2007 16:44:23 +0200, Rik wrote:
> $link = htmlspecialchars(<path>).'?'.urlencode(<query_string>);

Damn, damn, damn, I'm gonna stop posting, I'm unusually thick today.

Not the entite querystring should be encoded obviously, only the 'name'
and 'value' part, not the & and '='..., and still as an attribute, all
should be hauled through htmlspecialchars()....

Last one before I leave:
$url = htmlspecialchars(
rawurlencode(<path>).'?'
.rawurlencode(<name>).'='.rawurlencode(<value>
.'&'
.rawurlencode(<name>).'='.rawurlencode(<value>));
--
Rik Wasmus
 >> Stay informed about: Problem with links with form data 

On Wed, 01 Aug 2007 16:51:59 +0200, Rik wrote:
> rawurlencode(<path>).'?'

I give up....
Anyone who doesn't seem retarder care to explain?

In the mean while, I'm gonna sit in a corner and cry.
--
Rik Wasmus
 >> Stay informed about: Problem with links with form data 

On Aug 1, 10:00 am, Jerry Stuckle wrote:

>
> If the variables and/or values have non-alphanumeric characters, are
> they properly encoded? I've seen this, for instance, when a value
> contains a space instead of the correct %20.
>

That was it. I was passing a url like path=http://www.mydomain.com ,
so now I encoded it . Strange is it worked fine for so many years, but
seems some browser/servers have problems with it.
 >> Stay informed about: Problem with links with form data 

Rik wrote:
> On Wed, 01 Aug 2007 16:51:59 +0200, Rik wrote:
>> rawurlencode(<path>).'?'
>
> I give up....
> Anyone who doesn't seem retarder care to explain?
>
> In the mean while, I'm gonna sit in a corner and cry.

Erwin passes Rik a beer and a nice quite corner to relax in.

Regards,
Erwin Moller
 >> Stay informed about: Problem with links with form data