CGI base URL behaviour

[Ed McNierney]

Bart -

And would you expect the same ServiceException to be raised if the URL were http://www.google.com ?

I don't think it's reasonable to expect an HTTP request that isn't clearly an OGC service request to return an OGC service error.  In essence, it's suggesting that ALL HTTP requests that aren't OGC requests should return OGC ServiceExceptions, and that would make the WWW rather unhelpful <g>.

I don't see how MapServer - in the scenario you describe - would be able to deduce that the HTTP GET request was intended to be an OGC request.

        - Ed

Ed McNierney
President and Chief Mapmaker
TopoZone.com / Maps a la carte, Inc.
73 Princeton Street, Suite 305
North Chelmsford, MA  01863
ed at topozone.com
(978) 251-4242

-----Original Message-----
From: UMN MapServer Developers List [mailto:MAPSERVER-DEV at LISTS.UMN.EDU] On Behalf Of Bart van den Eijnden
Sent: Monday, November 15, 2004 2:22 AM
To: MAPSERVER-DEV at LISTS.UMN.EDU
Subject: Re: [UMN_MAPSERVER-DEV] CGI base URL behaviour

Hi Tom,

I agree with you that a ServiceException should be raised according to the spec.

I don't think the OGC CITE tests have a testcase for this though.

I would have excepted the OGC specs to have an exception code defined for this type of exception (something like InvalidRequest) but this is not the case.

Best regards,
Bart

> Hi,
>
> When publishing my URL for OGC:WMS, OGC:WFS and OGC:WCS, i.e. mapserv
> CGI, I provide the following information:
>
> http://somehost/someurl
>
> and that's it.  If I invoke the exact URL as per above, I get:
>
> "No query information to decode. QUERY_STRING is set, but empty."
>
> ...which we all know what this is and what it means.
>
> In an OGC scenario, I believe that an OGC Service Exception should be
> returned, as the URL above is missing keywords for a given OWS request.
> Is this anywhere in the OGC CITE assertions?
>
> In a non-OGC scenario (pure MapServer CGI), what is returned has
> become pretty defacto (though I would argue for XML-based MapServer
> error reporting, but that's another story).
>
> I'm interested in what comments others have.
>
> Cheers
>
> ..Tom
>
>