That's only in your html. For example when you use a.get('href') it will
return the value without the entities: http://jsfiddle.net/A5Naa/On Tue, Feb 7, 2012 at 11:55 AM, stratboy <[email protected]> wrote: > It would be nice if & (the entity) would be read like a simple '&' > and thus ignored in the results. Also for the fact that '&' > validates, '&' does not validate. > > On 7 Feb, 10:02, Sanford Whiteman <[email protected]> wrote: > > > Hi! I've found that parseQueryString doesn't correctly parse query > > > string with & entities, like this: > > > > Entities have no special meaning in URLs. > > > > > > AWSAccessKeyId=1RZJ66V99R267YCDQSG2&Expires=1330162525&Signature=F > > > %2FbNMruOog2ejsspsaZTBKVkIHM%3D > > > The output of parseQueryString would be this: > > > Object { AWSAccessKeyId="1RZJ66V99R267YCDQSG2", amp=[2], > > > Expires="1330162525" ... } > > > where you can see amp=[2] > > > > `amp` has no value (it is passed twice with just the name). I agree > > that there's something weird about the [2] (which looks like [true + > > true], haven't looked at the code). Having it be set to null or > > undefined makes more sense, so you can find it on the object but with > > no value. What are you expecting? > > > > -- Sandy >
