-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greg,
Gregory Gerard wrote: | A follow up question for 100: why does the spec define this at all I think "they" explicitly set the session id parameter and cookie name so that different implementations would be compatible. In some cases, you may need to hand-code a URL and preserve the jsessionid parameter. If you switched servlet containers, you'd have to go back and find all those references and change them. I don't find that too compelling of a reason, though. | and why does Tomcat not let me work around it when it happily lets me | violate other parts of the spec? Can you provide a few examples of how Tomcat allows you to violate other parts of the specification? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkerHBkACgkQ9CaO5/Lv0PAyagCcDSsop9crxgDcU3hxHyYdVgJg JS0An0YabcqZMULmH8JF+ghVWXA7HCXE =bpY0 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
