LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


ZNG@C4VLPLISTSERV01.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  August 2006

ZNG August 2006

Subject:

Implementing SRU GET/POST/SOAP servers, was: Diagnostic missing for SRU SOAP malformed packages ??

From:

marc <[log in to unmask]>

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Fri, 18 Aug 2006 14:59:41 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (144 lines)

Robert Sanderson wrote:

> 
>> In case of a HTTP POST request, I need to open the POST'ed data, to see
>> what I should do - and that's application logic!
> 
> No, you can and should check the content-type header.
> 
> See:  http://www.loc.gov/standards/sru/sru-post.html

That was what I meant, but did not write clearly.

Still, you are chickening out.

I got no clear answers for the following situations a
SRU GET/POST/SOAP server should survive:

a) A HTTP POST request is not in the headers specified of content type
    application/x-www-form-urlencoded  SRU/POST or
    text/xml            SRU/SOAP or
    application/soap+xml   SRU/SOAP

    what's the correct behaviour ?? I suppose it's

    HTTP error 415 Unsupported Media Type

b) A HTTP POST request is of content type text/xml or
    application/soap+xml, but the posted data can not be parsed as XML

    I see no HTTP error which fits the bill at

    http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

    but I might have missed something. Maybe the best here is

    HTTP error 400 Bad Request   ???


c) A HTTP POST with correct text/xml headers and parsable XML, but is
    just no SOAP

     Nobody asked for SOAP, so this should be a HTTP error rather than a
     SOAP error, right ?? Which one ??

d) A HTTP POST with correct  application/soap+xml headers and parsable
     XML, but is just no SOAP with Envelope and Body wrappers.

     Now a SOAP error is appropriate, I guess.

     http://www.w3.org/TR/soap/ is the page.

     The primer
     http://www.w3.org/TR/2003/REC-soap12-part0-20030624/
     Section 2.3 "Fault Scenarios" seems not to give a clear answer.

     There it is stated that the Body has to carry a

     <env:Fault>
       <env:Code>
          <env:Value>
        ...
       <env:Reason>
       ...

    XML block, The env:Code sub-element of env:Fault is itself made up of
    a mandatory env:Value sub-element, whose content is specified in the
    SOAP specification (see SOAP Part 1 section 5.4.6) as well as an
    optional env:Subcode sub-element.

    Looking at that reference,
    http://www.w3.org/TR/2003/REC-soap12-part1-20030624/#faultcodes

    I would guess it's the "Sender" fault code which needs to be send ??

    What's your advice here ??



e) Your example of an invalid SRU GET request

    http://foo.com/sru?version=1.1

    which does not state any operation, must issue a fatal diagnostic.

    7 Mandatory parameter not supplied

    That's clear.

    I presume you wrap this in a <srw:explainResponse>,

    as there are only scan, search and explain to choose from, and the
    two others feel quite odd to wrap it into, right ??

    But this means assuming the operation 'explain' if you can not
    determine which operation to use ??


Cheers, Marc Cromme


> 
>> 3) if I get something else in the POST'ed data - I do what ??
>> How should the server respond ??
> 
> Whatever a SOAP server would do with a broken request, which I'm sure is
> defined in the SOAP w3 docs.
> 
>> If no valid operation is parsed (due to empty parameter SRU GET list),
>> explain is assumed anyhow ..
> 
> That's not exactly how it works.
> 
> Either there are no parameters, or there's an operation parameter.
> Anything else is a broken client.
> 
> eg:
>   http://foo.com/sru?version=1.1&query=cat&recordSchema=dc
> 
> is just not a valid SRU URL. Nor is:
>   http://foo.com/sru?version=1.1
> 
> 
> Rob
> 


-- 

Marc Cromme, cand. polyt, Ph.D
Senior Developer, Project Manager

Index Data Aps
K°bmagergade 43, 2
1150 Copenhagen K.
Denmark

tel: +45 3341 0100
fax: +45 3341 0101

http://www.indexdata.com

INDEX DATA Means Business
for Open Source and Open Standards

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager