This problem should be handled by modifying the php.ini.  In my experience W3C is a 
whiney bitch that always gets it's way. Just throw this code on all your pages (or 
better yet, in a header) and the problem will go away.

// The communists at W3C don't like the ampersand, so let's make sure it isn't used.
ini_set('arg_separator.output', '&');

Cheers,
Nathan Taylor
  ----- Original Message ----- 
  From: Burhan Khalid 
  To: [EMAIL PROTECTED] ; [EMAIL PROTECTED] 
  Sent: Friday, October 24, 2003 3:43 PM
  Subject: Re: [PHP] w3c-compliant form-action parameters


  Chris Shiflett wrote:

  > --- Timo Boettcher <[EMAIL PROTECTED]> wrote:
  > 
  >>I am trying to get my pages through the w3c-validator for html.
  >>It doesn't like my
  >><FORM action="mypage.php?para1=val1&para2=val2">
  >>Changing & to &amp; got my page through the validator, but broke
  >>my app, which seems not to be getting any parameters over URL
  >>anymore.
  > 
  > 
  > I find that *very* hard to believe. I'm not aware of any browser that
  > mishandles HTML entities. Basically, when you say this:
  > 
  > action="/mypage.php?para1=val1&amp;para2=val2"
  > 
  > Your browser's HTTP request line will appear as:
  > 
  > /mypage.php?para1=val1&para2=val2
  > 
  > So, by the time PHP sees it, everything is the same either way. My guess is
  > that you have some other problem.

  I agree with Chris. This is not a browser problem.

  However, there is a php.ini setting that will allow you to set the 
  separator for get requests, but I suggest you investigate this problem 
  further.

  -- 
  Burhan Khalid
  phplist[at]meidomus[dot]com
  http://www.meidomus.com

  -- 
  PHP General Mailing List (http://www.php.net/)
  To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to