| 06:37:22 | akrherz: | how does one handle doing CGI variable substitution parameter name case sensitivity ? arc catalog wants to uppercase all parameter names, while others wfs clients don't seem to be. |
| 06:46:36 | danmo: | make all $VARS% uppercase all the time? |
| 06:46:45 | danmo: | I mean %VARS% |
| 06:46:53 | danmo: | or do not use ArcCatalog? ; ) |
| 06:47:47 | akrherz: | hehe, that'd be nice. I'm just going to uppercase them and break the other clients, if they follow the onlineresource, they should get the updated case |
| 06:51:02 | danmo: | uh? vendor-specific parameters included in the online resource ( that's what %VARS% are ) should not be modified at all by the client... so what Arc Catalog does is illegal according to the WMS spec ( well, I'm 99% sure of that )... I doubt that any other client does the same as well but the reverse way ( i.e. turning everything lowercase ) |
| 06:54:28 | danmo: | OGC WMS 1.1.1 section 6.2.2 says: "An Online Resource URL intended for HTTP GET requests is in fact only a URL prefix to which additional parameters are appended in order to construct a valid Operation request. A URL prefix is defined as an opaque string including the protocol, hostname, optional port number, path, a question mark '?', and, optionally, one or more serverspecific parameters ending in an ampersand '&'." |
| 06:54:36 | danmo: | http://portal.opengeospatial.org/files/?artifact_id=1081&version=1&format=pdf |
| 06:55:35 | danmo: | The key part here is "opaque string" ... this means that if you put your %vars% in the online resource, Arc Catalog, or any other client is __NOT__ allowed to touch them |
| 07:51:12 | akrherz: | thanks danmo, sorry I ran out for an hour. I'll bug esri and see if it takes as long to fix as the WMS 1.1.0 bug : ) |
| 07:51:37 | danmo: | good luck! ; ) |