No subject

6.2.1 Reserved characters in HTTP GET URLs=20
The URL specification [IETF RFC 2396] reserves particular characters as
significant and=20
requires that these be escaped when they might conflict with their =
defined
usage.  The=20
present WMS specification explicitly reserves several of these =
characters
for use in the=20
query portion of HTTP GET requests.  When the characters "?", "&", =
"=3D", "/",
":" and ","=20
appear in one of the roles defined in Table 1, they are to appear =
literally
in the URL. =20
When such characters appear elsewhere (for example, in the value of a
parameter), they=20
are to be encoded as defined in [IETF RFC 2396].=20

This means the OpenLayers API is wrong to encode image/png or EPSG:4326 =
etc.

Mit freundlichen Gr=FCssen

Arnd Wippermann
http://gis.ibbeck.de/ginfo/






-----Urspr=FCngliche Nachricht-----
Von: crschmidt at metacarta.com [mailto:crschmidt at metacarta.com]=20
Gesendet: Dienstag, 16. Oktober 2007 21:18
An: Arnd Wippermann
Cc: 'huub fleuren'; users at openlayers.org
Betreff: Re: [OpenLayers-Users] redirected maprequests

On Tue, Oct 16, 2007 at 07:02:51PM +0200, Arnd Wippermann wrote:
> With OL Version 1.0 the WMS works all right.
> =20
> Looking at the code I don't find where the encoding takes places.=20
> Where I have to look?

OpenLayers.Util.getParameterString.=20

Regards,
--
Christopher Schmidt
MetaCarta