(I don't know about W3C, but) Yes, it can. I have been forced to use & in the past where IE was resolving GET parameters to escape characters, even though the semi colon was missing. In my case I had a parameter called quoteId, so the request ...?abc=123"eId=456 became ...?abc=123"eId=456
Changing the request to ...?abc=123&quoteId=456 fixed it just fine. WIll anecdotal evidence do? -----Original Message----- From: Geoff Howard [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 15 January 2003 11:27 AM To: [EMAIL PROTECTED] Subject: & in url [WAS: file generator error] I would regard the behavior below to be incorrect - so the million dollar question is what is the correct behavior: Can GET parameters be separated by & instead of & according to the W3C, etc? Don't have time to look it up myself - does anyone know for sure? Geoff > -----Original Message----- > From: Joerg Heinicke [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 14, 2003 3:14 PM > To: [EMAIL PROTECTED] > Subject: Re: file generator error <snip/> > If I type > http://127.0.0.1:8080/cocoon/joerg/test?test=test&test2=test2 I get > (IMO also) expected > > <requestParameters> > <parameter name="amp;test2"> > <value>test2</value> > </parameter> > <parameter name="test"> > <value>test</value> > </parameter> > </requestParameters> > > because & as delimiter for the parameters (not &), so amp; must be > the beginning of the next parameter name. --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
