php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Request #23961 arg_separator.output default value not html compliant
Submitted: 2003-06-02 13:24 UTC Modified: 2003-06-02 15:29 UTC
From: wallacebw at yahoo dot com Assigned:
Status: Not a bug Package: Feature/Change Request
PHP Version: 4.3.2 OS: RedHat 8 W/Apache 2.0.40
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: wallacebw at yahoo dot com
New email:
PHP Version: OS:

 

 [2003-06-02 13:24 UTC] wallacebw at yahoo dot com 
Hello,

The default value for arg_separator.output is currently '&' which although functional is incorrect acurding to w3c.org's html 4.01 specification.  the correct code to use in links (according to w3c) is the html special char '&'.  Is there any reason that this is not the default behavior?

i.e.  

URL's rewritten by PHP's session url rewriter appends 

'&PHPSESSID=*sessionid*'...  odviously *sessionid* would be the true session ID...   

This will fail the W3C html validator.  However if you issue a 

ini_set("arg_seperator.output", "&");

first (thus replacing '&' with '&') php returns

'&PHPSESSID=*sessionid*'.

 which validates fine.  

Again, this is not so much a functionality issue.. it's more Of a conformance issue.  

Thanks,
Brian

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-06-02 13:27 UTC] sniper@php.net 
You can change it yourself very very easily..
 [2003-06-02 14:09 UTC] wallacebw at yahoo dot com 
That is a cop-out answer... If there is no reason to not to comply with the standard than you (the PHP project) should make all efforts to do so.
 [2003-06-02 14:28 UTC] derick@php.net 
RTFM :)
http://www.php.net/manual/en/configuration.directives.php#ini.arg-separator.output
 [2003-06-02 15:20 UTC] wallacebw at yahoo dot com 
I DID RTFM... Read my first post...

Still no reason to deviate from standards as been provided.  

You should strive to remain standards compliant.   Case and Point... Microsoft

It's a simple fix...  provide me with an explanation as to why this should not be corrected rather than showing me a work-around for the problem. (which as my first post shows I am already using).  If there is an underlying reason for the current setting I would like no know what it is... if not than this is a bug that needs to be corrected.  

I am not trying to be difficult but rather point out an issue that appears to have been overlooked...    

Brian
 [2003-06-02 15:23 UTC] derick@php.net 
blah blah blah standard blah compliant blah.

As long as there are no browser NOT understanding it we're not going to change it as we have reports that some browser do NOT support the & style. (Yes, I know they are broken). If you want to be standards compliant, just change the setting.

Derick
 [2003-06-02 15:29 UTC] derick@php.net 
Oh, if you would have searched the bug database first (try separater as keyword) you would have found bugs #18993, #20575, #21722 and if you would have searched for "amp" you'd have found #9421, #20798, #20418, #18205, #15804, #9723 and more...

Derick
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Apr 27 14:01:30 2024 UTC