[CITE-Forum] url-encoding spaces in WCS 1.0.0 tests.

Richard Martell rmartell at galdosinc.com
Mon Mar 4 19:12:06 EST 2013


Larry,


A coverage name can be any xs:string value, so spaces are allowed.
In the query part of the request URI spaces must be percent-encoded 
per RFC 3986 <http://tools.ietf.org/html/rfc3986#section-3.4>.


pchar = unreserved / pct-encoded / sub-delims / ":" / "@"
query = *( pchar / "/" / "?" )


CITE-778:
<https://portal.opengeospatial.org/?m=projects&a=view&project_id=85&tab=5&act=details&issue_id=778>


--
Richard

> -----Original Message-----
> From: 
> cite-forum-bounces+rmartell=galdosinc.com at lists.opengeospatial
> .org 
> [mailto:cite-forum-bounces+rmartell=galdosinc.com at lists.openge
> ospatial.org] On Behalf Of Larry Gilliam
> Sent: Monday, 04 March, 2013 13:50
> To: cite-forum at lists.opengeospatial.org
> Subject: [CITE-Forum] url-encoding spaces in WCS 1.0.0 tests.
> 
> Hello,
> 
> Some of our coverages have spaces in the names, which I *think* is
> allowed, but the cite teamengine tests for WCS 1.0.0 don't seem to
> url-encode the names when they send them as GET parameters, so they
> don't make it to the server intact.
> 
> Incidentally the tests do url-encode some characters that aren't
> necessary to encode afaik ( e.g. colons ).
> 
> Thanks,
> -Larry
> _______________________________________________
> CITE-Forum mailing list
> CITE-Forum at lists.opengeospatial.org
> https://lists.opengeospatial.org/mailman/listinfo/cite-forum
> 


More information about the CITE-Forum mailing list