Opened 19 years ago
Closed 19 years ago
#1253 closed defect (fixed)
[WFS-server] template error when issuing DescribeFeatureType via POST
Reported by: | tomkralidis | Owned by: | mapserverbugs |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | WFS Server | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: |
Description
I'm submitting this on behalf of a partner/colleague (on cc list) When issuing a DescribeFeatureType as HTTP POST: http://www.bsc-eoc.org/cgi-bin/bsc_eoc.asp Response is: <HTML> <HEAD><TITLE>MapServer Message</TITLE></HEAD> <!-- MapServer version 4.4.0 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP OUTPUT=PDF OUTPUT=SWF SUPPORTS=PROJ SUPPORTS=FREETYPE SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE --> <BODY BGCOLOR="#FFFFFF"> mapserv(): Web application error. No template provided. <br> </BODY></HTML> Using: MapServer 4.4.0 Windows Server 2003 IIS I will include a zipfile testcase of the mapfile in question, and sample HTML with a POST request.
Attachments (1)
Change History (5)
by , 19 years ago
Attachment: | testcase.zip added |
---|
comment:1 by , 19 years ago
Tom, we've had reports of similar issues in the past that were caused by proxies or firewalls that didn't let XML POST requests go through. I would suggest that you test this first directly on the server, or on the same local network, or on one of your own servers to confirm that this is not a proxy of firewall issue. BTW, they use an ASP wrapper: are you sure that the wrapper lets the XML post information go through and uses the correct MIME types?
comment:2 by , 19 years ago
I just tested on my own (shell script redirect to mapserv style), and got no problems. Their ASP wrapper is verbatim as per: http://mapserver.gis.umn.edu/doc44/wms-server-howto.html#onlineresourceurl I tried this against their WFS (HTTP POST), but pointing directly to the binary with map= in the URL (no ASP wrapper). Worked fine. I tried the same test on a few other WMSs out there with the ASP wrapper script, and get the same problem behaviour. So I would say there is some problem with the ASP wrapper script. Perhaps an ASP guru can advise on what's fouling up.
comment:3 by , 19 years ago
It seems that the wrapper script in the howto si built only for the GET method (it reads QUERY_STRING, and it seems to initialize the HTTP object with a hardcoded GET method. Unfortunately I am no ASP expert so I can't help. I don't even remember who contributed that script. Maybe you could post a question to the list?
comment:4 by , 19 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
We tried with a modified ASP wrapper which handles GET and POST and all works fine. I've posted the fix in bug 1254. Closing this bug.
Note:
See TracTickets
for help on using tickets.
testcase for this bug