[fdo-trac] #607: WMS: Provider does not URL encode GetMap Requests

[FDO]

#607: WMS: Provider does not URL encode GetMap Requests
--------------------------+-------------------------------------------------
 Reporter:  gregboone     |         Owner:  grfegboone
     Type:  defect        |        Status:  new       
 Priority:  minor         |     Milestone:  3.5.0     
Component:  WMS Provider  |       Version:  3.5.0     
 Severity:  3             |    Resolution:            
 Keywords:                |   External_id:            
--------------------------+-------------------------------------------------
Old description:

> Connect to:
>
> http://62.214.147.252:8080/cgi-
> bin/mapserv.exe?map=C%3a%5cProgram+Files%5cms4w%5cApache%5chtdocs%5cBB2009%5cBB2009.map&version=1.1.1
>
> Execute GetMap Request
>
> The WMS Server fails to return data from the GetMap request.
>
> Looking at the GetMap request and the reply from the WMS server. The WMS
> server replies with:
>
> ‘msEvalRegex(): Regular expression error. String (C:\Program) failed
> expression test.?
>
> and when looking in the GetMap request generated by Map it looks like the
> path is not masked correctly. It should be:
> C%3a%5cProgram+Files%5cms4w%5cApache?but it looks like 'C:\Program
> Files\...? The space in the file name could be the cause of the issue -
> it should be masked correctly.

New description:

 Connect to:

 http://62.214.147.252:8080/cgi-
 bin/mapserv.exe?map=C%3a%5cProgram+Files%5cms4w%5cApache%5chtdocs%5cBB2009%5cBB2009.map&version=1.1.1

 Execute a !GetMap Request

 The WMS Server fails to return data from the request.

 Looking at the request and the reply from the WMS server. The WMS server
 replies with:

 ‘msEvalRegex(): Regular expression error. String (C:\Program) failed
 expression test.?

 When looking at the !GetMap request generated by the application, it looks
 like the path is not masked correctly. It should be:
 C%3a%5cProgram+Files%5cms4w%5cApache?but it looks like 'C:\Program
 Files\...? The space in the file name could be the cause of the issue - it
 should be masked correctly.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/607#comment:1>
FDO <http://fdo.osgeo.org/>
Feature Data Objects