On 16-02-16 21:14, Ben Caradoc-Davies wrote: > The encoding of the child href is very thin (only ampersand is > replaced). Encoding " to " might give a better error message. And > what about percent-encoding? What happens to spaces or # or other > characters in resource names? You have a point. What I am doing here is escaping the GET argument ampersands for HTML. But we should really convert the resource name (for all three formats) to use % for special characters (including ampersand), shouldn't we?
Regards Niels ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
