PHP-/SWIG-Mapscript WFS GetPropertyValue: HTTP Headers in Textbody about mapserver HOT 5 CLOSED

Regular http query from the demo server does not print http headers

https://demo.mapserver.org/cgi-bin/wfs?SERVICE=WFS&VERSION=2.0.0&REQUEST=getfeature&TYPENAME=foo&MAXFEATURES=100

Could you try similar query with your server? If issue appears to be something specific to Mapscript, please try to write ans attach a re-producible example. It would be excellent if you could make the issue to happen with demo.mapserver.org.

from mapserver.

OK, it seems that msIO_getAndStripStdoutBufferMimeHeaders solves the problem, as described here: #6762

For testing (to demonstrate the problem) I used the following code (SWIG-Mapscript):

<?php 

$mapfile = <<<MAPFILE
MAP
  WEB
    METADATA
      "ows_enable_request"	"*"
      "wfs_onlineresource"	"http://127.0.0.1/cities"
    END # METADATA
  END # WEB

  LAYER
    CONNECTION "cities.gml"
    CONNECTIONTYPE OGR
    ENCODING "UTF-8"
    METADATA
      "gml_include_items"	"all"
    END # METADATA
    NAME "cities"
    PROJECTION
      "init=epsg:4326"
    END # PROJECTION
    TYPE POINT
  END # LAYER
END
MAPFILE;

$objMap = mapscript::msLoadMapFromString($mapfile, NULL);

$request = new OWSRequest();
foreach ($_GET as $key => $value) $request->setParameter($key, $value);

mapscript::msIO_installStdoutToBuffer();

$objMap->owsdispatch($request);

$contenttype = mapscript::msIO_stripStdoutBufferContentType();
mapscript::msIO_stripStdoutBufferContentHeaders();

//to show the plain output in the browser:
header('Content-Type: text/plain');

print mapscript::msIO_getStdoutBufferBytes();

The following request works as expected:
example.php?SERVICE=WFS&REQUEST=GetFeature&VERSION=2.0.0&TYPENAMES=cities

This request outputs the HTTP-headers in the HTTP-Body:
example.php?SERVICE=WFS&REQUEST=GetFeature&VERSION=2.0.0&TYPENAMES=foo

As said above, with msIO_getAndStripStdoutBufferMimeHeaders it works, but the function didn't exist in PHP-Mapscript.
I agree with the author of #6762 in that the functionnames are misleading.
Any documentation would be fine.

from mapserver.

@ghschier thanks for the research. I'm sure we'd be open to renaming these confusingly-named functions, but that would have to be for a MapServer 9.0 release. Would you mind filing a new issue for the renaming (and stating the new and old names there)? Thanks.

Regarding documentation (it sounds like it is perfect timing as it is so fresh in your mind) we're always open for pull requests.

from mapserver.

Opened new issue #6944.

from mapserver.

Thanks @ghschier the new issue is very clear, I'd be in support of those changes.

Closing this issue here.

from mapserver.