#28551 [Bgs]: session.use_trans_sid bug

ID: 28551 User updated by: irie at gmx dot de Reported By: irie at gmx dot de Status: Bogus Bug Type: Session related Operating System: Linux PHP Version: 4.3.6 New Comment: The arg_separator.input option isn't the solution, because it didn't accept strings as seperator but only single characters. On the other hand if php only supports single charcters as arg-sepereators (and &amp; as an exception) I can easily live with that but this could be better documented... Previous Comments: ------------------------------------------------------------------------ [2004-05-27 22:56:28] iliaa@php.net Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php If you are using &#38;, you need to tell PHP that is what you are using via arg_separator.input ini option. ------------------------------------------------------------------------ [2004-05-27 22:53:25] irie at gmx dot de Description: ------------ I faced a problem when using &#38; as the argument-seperator in URIs with session.use_trans_sid turned on. According to the w3-specs (see http://www.w3.org/TR/html4/appendix/notes.html#h-B.2.2 ) &#38; is equivalent to &amp; so I think it should work. But the arguments are getting mixed up. With &amp; as the seperator it's working well. It's the same with php5.0RC2. Expected result: ---------------- <a href="toggle.php?a=table&#38;p=5&#38;d=open&#38;sid=2dba9000ab000190477a57d27433f121"> Actual result: -------------- <a href="toggle.php?a=table&&#38;sid=2dba9000ab000190477a57d27433f121#38;p=5&#38;d=open"> (with arg_separator.output = "&#38;") ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=28551&edit=1