Even,
Another strange thing with GDAL WFS driver. Earlier it did not try to
access the HEAD of a XXX.resolved.gml and now it does:
Here's an excerpt from my server logs. These calls are created by GDAL,
the first is a good GetFeature call, which gets 215633 bytes of GML and
the next is bogus. I can see this made up in ogrgmldatasource.cpp but do
not understand why. In February this did not happen and GDAL parsed the
GML the WFS provided fine (it actually created by GDAL too).
213.157.86.72 - ajolma [21/May/2013:00:02:56 +0300] "GET
/OILRISK-protected/wfs.pl?SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&TYPENAME=OILRISK.vtest.geom
HTTP/1.1" 200 215633
213.157.86.72 - ajolma [21/May/2013:00:02:58 +0300] "HEAD
/OILRISK-protected/wfs.pl?SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&TYPENAME=OILRISK.vtest.resolved.gml
HTTP/1.1" 200 -
Do you have an idea what's going on here?
Thanks,
Ari
On 05/20/2013 11:13 PM, Even Rouault wrote:
My question is, is CPL of GDAL doing anything related to OpenSSL (like
setting callbacks)
No, to the best of my knowledge, there's nothing explicitely related to OpenSSL
in CPL use of curl. CPL code sets callbacks, but there are specific to the Curl
contexts created by CPL.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
