Bug #18205 Updated: Session ID added to URL not HTML compliant
| From: | philip@php.net | Date: | Mon, 08 Jul 2002 05:58:52 +0000 |
| Subject: | Bug #18205 Updated: Session ID added to URL not HTML compliant | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-13483@lists.php.net to get a copy of this message | ||
ID: 18205
Updated by: philip@php.net
Reported By: hectorp@buckfoodsvc.com
Status: Bogus
Bug Type: Session related
Operating System: Suse Linux 8
PHP Version: 4.1.2
New Comment:
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
Previous Comments:
------------------------------------------------------------------------
[2002-07-07 06:25:45] 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-07 04:01:17] mfischer@php.net
Why do we have a "arg_separator.output" ini setting or what am I
missing here?
------------------------------------------------------------------------
[2002-07-07 01:41:56] hectorp@buckfoodsvc.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 01:36:41] 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:22:28] hectorp@buckfoodsvc.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.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/18205
--
Edit this bug report at http://bugs.php.net/?id=18205&edit=1