Interesting. If the key is being sent raw as part of a url with the + sign unencoded, it may be interpreted as a space. Is it possible that is happening in this case?
On 2011-01-13, Greg <[email protected]> wrote: > > I was messing around with things and noticed that the XML passed to the > server is 8 characters long for the features that are returned correctly and > only 7 characters long for the ones that are not. It looks like the plus > sign is the offending character. I look at the encoded xml on the client > side and it looks something like this : +goAAA== and on there server side > after decode it have: goAAA==. I have looked at several and the all the > offending ones I have found start with +. There is probably of a better way > to send the xml to the server but this is how I am doing it: > > client side: var selectionXML = > encodeURI(viewerFrame.GetMapFrame().GetSelectionXML()); > > server side: String selectionXML = > Server.UrlDecode(Request.Form.Get("sel")); > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/selectionXML-Problem-tp5920249p5920609.html > Sent from the MapGuide Users mailing list archive at Nabble.com. > _______________________________________________ > mapguide-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapguide-users > _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
