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

go to bug id or search bugs for

Bug #18205 Session ID added to URL not HTML compliant
Submitted: 2002-07-06 23:20 UTC Modified: 2002-07-08 01:58 UTC
Votes:3
Avg. Score:1.0 ± 0.0
Reproduced:3 of 3 (100.0%)
Same Version:3 (100.0%)
Same OS:3 (100.0%)
From: hectorp at buckfoodsvc dot com Assigned:
Status: Not a bug Package: Session related
PHP Version: 4.1.2 OS: Suse Linux 8
Private report: No CVE-ID: None
View Add Comment Developer Edit
 [2002-07-06 23:20 UTC] hectorp at buckfoodsvc dot com 
The session id is added with a raw & (ampersand) character to anchor links, rather than & (ampersand+"amp;") as required to be compliant, as reported by the w3's HTML validator.

By the way, I'd have searched to see if it's been reported before, but the search function called me a "bad database hacker" when I attempted to view the next page. :-(

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-07-06 23:24 UTC] sniper@php.net 
Sorry, but the bug system is not the appropriate forum for asking
support questions. Your problem does not imply a bug in PHP itself.
For a list of more appropriate places to ask for help using PHP,
please visit http://www.php.net/support.php

Thank you for your interest in PHP.
 [2002-07-06 23:29 UTC] hectorp at buckfoodsvc dot com 
What the hell are you talking about?  I just reported a bug in the way php transparently adds the session id to a link in a page a php program generates; I didn't ask a support question or _any_ question at all.  Pay attention, junior.
 [2002-07-07 01:15 UTC] sniper@php.net 
Sorry, but the bug system is not the appropriate forum for asking
support questions. Your problem does not imply a bug in PHP itself.
For a list of more appropriate places to ask for help using PHP,
please visit http://www.php.net/support.php

Thank you for your interest in PHP.
 [2002-07-07 01:22 UTC] hectorp at buckfoodsvc dot com 
Perhaps some actual developer would like to take note of this bug and fix it.  Or not.  Perhaps I'd like to go back to C.  Sheesh.
 [2002-07-07 01:36 UTC] rasmus@php.net 
Can you guarantee that making this change would not break any clients out there?  I know what the standard says, and I know what the validators say, but I really don't care.  I care a lot more about what works.  The current mechanism works everywhere and as such the motivation to change it just because a validator says to is nonexistant.
 [2002-07-07 01:41 UTC] hectorp at buckfoodsvc dot com 
"Can you guarantee that making this change would not break any clients out there?"

I can't find one that cares -- Opera, Mozilla, Konqueror, Lynx, Links, IE, etc. all work correctly either way.  Thus it would seem to be the smart thing to do to comply with the standards, as those clients may _not_ work with noncompliant URLs later.

However, note that I merely reported the bug -- what you do with it is up to you.  There are lots of programming languages out there if it comes to that, and I'm capable of making my choices and living with them.  I just didn't much appreciate being told it wasn't a bug but a request for "support."

I take it that PHP doesn't stand for "Pretty Happy Programmers."
 [2002-07-07 04:01 UTC] mfischer@php.net 
Why do we have a "arg_separator.output" ini setting or what am I missing here?
 [2002-07-07 06:25 UTC] derick@php.net 
Yes, we have that ini setting for that, so you can work around it if you like (or care).

Derick
 [2002-07-08 01:58 UTC] philip@php.net 
This was checked as a support question, "not developer issue*" specifically.  It was seen as a support question because a solution to your problem exists in php.ini.  Nothing personal.

Although, this stems from a documentation problem, see bug #15603 for details.  This documention problem is fixed in CVS.

* http://bugs.php.net/quick-fix-desc.php
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sun Jun 02 03:01:30 2024 UTC