[TinyOWS-users] Wrong HTTP request Method?

[Rahkonen Jukka]

Hi,

I believe I managed to capture the whole message:

POST http://188.64.1.61/cgi-bin/tinyows HTTP/1.1
Accept-Encoding: gzip, deflate, bzip2
Content-Type: text/xml; charset=utf-8
User-Agent: Cadcorp SIS Map Browser
Host: 188.64.1.61
Content-Length: 4181
Connection: Keep-Alive
Pragma: no-cache

<?xml version="1.0" encoding="UTF-8"?>
<wfs:GetFeature service="WFS" version="1.0.0" outputFormat="GML2" maxFeatures="20" xmlns:gml="http://www.opengis.net/gml" xmlns:ogc="http://www.opengis.net/ogc" xmlns:wfs="http://www.opengis.net/wfs" xmlns:tows="http://www.tinyows.org/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/ogc http://schemas.opengis.net/filter/1.0.0/filter.xsd http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.0.0/WFS-basic.xsd">
    <wfs:Query typeName="tows:osm_point">
        <ogc:PropertyName>tows:osm_id</ogc:PropertyName>
        <ogc:PropertyName>tows:access</ogc:PropertyName>
        <ogc:PropertyName>tows:addr_flats</ogc:PropertyName>
        <ogc:PropertyName>tows:addr_housenumber</ogc:PropertyName>
        <ogc:PropertyName>tows:addr_interpolation</ogc:PropertyName>
        <ogc:PropertyName>tows:admin_level</ogc:PropertyName>
        <ogc:PropertyName>tows:aerialway</ogc:PropertyName>
        <ogc:PropertyName>tows:aeroway</ogc:PropertyName>
        <ogc:PropertyName>tows:amenity</ogc:PropertyName>
        <ogc:PropertyName>tows:area</ogc:PropertyName>
        <ogc:PropertyName>tows:barrier</ogc:PropertyName>
        <ogc:PropertyName>tows:bicycle</ogc:PropertyName>
        <ogc:PropertyName>tows:bridge</ogc:PropertyName>
        <ogc:PropertyName>tows:boundary</ogc:PropertyName>
        <ogc:PropertyName>tows:building</ogc:PropertyName>
        <ogc:PropertyName>tows:capital</ogc:PropertyName>
        <ogc:PropertyName>tows:construction</ogc:PropertyName>
        <ogc:PropertyName>tows:cutting</ogc:PropertyName>
        <ogc:PropertyName>tows:disused</ogc:PropertyName>
        <ogc:PropertyName>tows:ele</ogc:PropertyName>
        <ogc:PropertyName>tows:embankment</ogc:PropertyName>
        <ogc:PropertyName>tows:foot</ogc:PropertyName>
        <ogc:PropertyName>tows:highway</ogc:PropertyName>
        <ogc:PropertyName>tows:historic</ogc:PropertyName>
        <ogc:PropertyName>tows:horse</ogc:PropertyName>
        <ogc:PropertyName>tows:junction</ogc:PropertyName>
        <ogc:PropertyName>tows:landuse</ogc:PropertyName>
        <ogc:PropertyName>tows:layer</ogc:PropertyName>
        <ogc:PropertyName>tows:learning</ogc:PropertyName>
        <ogc:PropertyName>tows:leisure</ogc:PropertyName>
        <ogc:PropertyName>tows:lock</ogc:PropertyName>
        <ogc:PropertyName>tows:man_made</ogc:PropertyName>
        <ogc:PropertyName>tows:military</ogc:PropertyName>
        <ogc:PropertyName>tows:motorcar</ogc:PropertyName>
        <ogc:PropertyName>tows:natural</ogc:PropertyName>
        <ogc:PropertyName>tows:oneway</ogc:PropertyName>
        <ogc:PropertyName>tows:operator</ogc:PropertyName>
        <ogc:PropertyName>tows:poi</ogc:PropertyName>
        <ogc:PropertyName>tows:power</ogc:PropertyName>
        <ogc:PropertyName>tows:power_source</ogc:PropertyName>
        <ogc:PropertyName>tows:place</ogc:PropertyName>
        <ogc:PropertyName>tows:railway</ogc:PropertyName>
        <ogc:PropertyName>tows:ref</ogc:PropertyName>
        <ogc:PropertyName>tows:religion</ogc:PropertyName>
        <ogc:PropertyName>tows:residence</ogc:PropertyName>
        <ogc:PropertyName>tows:route</ogc:PropertyName>
        <ogc:PropertyName>tows:service</ogc:PropertyName>
        <ogc:PropertyName>tows:shop</ogc:PropertyName>
        <ogc:PropertyName>tows:sport</ogc:PropertyName>
        <ogc:PropertyName>tows:tourism</ogc:PropertyName>
        <ogc:PropertyName>tows:tunnel</ogc:PropertyName>
        <ogc:PropertyName>tows:waterway</ogc:PropertyName>
        <ogc:PropertyName>tows:width</ogc:PropertyName>
        <ogc:PropertyName>tows:wood</ogc:PropertyName>
        <ogc:PropertyName>tows:z_order</ogc:PropertyName>
        <ogc:PropertyName>tows:way</ogc:PropertyName>
<Filter xmlns="http://www.opengis.net/ogc">
  <BBOX>
    <PropertyName>tows:way</PropertyName>
    <gml:Box xmlns:gml="http://www.opengis.net/gml" srsName="EPSG:4326"><gml:coordinates>-180,-182.057142857143 180,182.057142857143</gml:coordinates></gml:Box>
  </BBOX>
</Filter>
    </wfs:Query>
</wfs:GetFeature>


This request seems to intruduce a new Content-Type variant, Content-Type: text/xml; charset=utf-8.
BBOX in this request does not hit my data, but otherwise I suppose it is OK.

-Jukka-




Olivier Courtin wrote:


> On Sep 27, 2010, at 8:14 PM, Rahkonen Jukka wrote:

> Hi Jukka,

>> I made another try by sending the xml that I captured from TinyOWS  
> logfile with the demo request web application which comes with  
> Geoserver installation. As a result I got features from TinyOWS. So  
> perhaps the Cadcorp client creates a valid request but it messes up  
> with headers or something. I need to write some mail to Cadcorp next.

> Yes TinyOWS check the headers send by client.

> On this point we are not that strict as several clients (including CITE)
> don't use the same headers values.
> And i'm not that sure that WFS 1.0.0 specify it (in 1.1.0 they did)

> So if you catch the headers used by CadCorp maybe we could add it too...


>  For information we already handle:
   - application/x-www-form-urlencoded	=> KVP (WFS 1.1.0)
   - text/xml							=> XML (WFS 1.1.0)
   - application/xml						=> XML (WFS 1.0.0 & CITE)
   - application/xml; charset=UTF-8		=> XML WFS 1.0.0 & CITE)
   - text/plain							=> XML WFS 1.0.0 & CITE)
   - text/xml, application/xml   			=> XML (Udig bug)

> --
> Olivier

_______________________________________________
TinyOWS-users mailing list
TinyOWS-users at lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tinyows-users