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:

Re: 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 12:30:17 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (151 lines)

Robert Sanderson wrote:
> It's a SOAP fault.  You wouldn't send a diagnostic for a malformed HTTP
> Get request or broken TCP/IP package, you allow the underlying
> transport mechanisms to take care of it, so we don't send a diagnostic
> for a malformed SOAP package.

I see your point that the application layer in many frameworks never 
will get the chance to handle a SOAP fault.

I forgot that I am one of the rare breed handconding the stuff .. buuut ..

> 
> Secondly, if the soap package is malformed, most toolkits will reject it
> before it ends up at the application layer, so many implementers would
> not be able to return the diagnostic anyway.

But there is a profound difference: if a client makes a HTTP request 
error, the usual HTTP error mechanisms apply, and HTTP status codes will 
be send back.

So far so good. Buuut .. but then I am out of luck:

If I want to make a SRU server which handles GET/POST/SOAP together,
I have at the application layer to decide what to do right after a 
sucessfull HTTP GET/POST

In case of a HTTP GET request, it must be SRU GET, no doubt, so I expect 
url-encoded parameters, and parse them, issuing usual diagnostics, if 
need be.

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!

1) if I get POST'ed url-encoded data, it must be SRU/POST, and I proceed 
exactly as by SRU/GET

2) if i get valid XML, _and_ a valid SOAP envelope in the XML, it must 
be SRU/SOAP, and I parse my XML request packages, and issue diagnostics 
if need be.

BUT

3) if I get something else in the POST'ed data - I do what ??

possible errors are:

- not mimetype urlencode or XML
- XML not proper XML
- proper XML. but no proper SOAP envelope


So, in the case of a SRU GET/POST/SOAP server, my server  _has_ to deal 
with these possible errors in my application layer.

Then what ??

How should the server respond ??

My proposal is to be kind, send an explain response, with some suitable 
diagnostic.

Better proposals for what to do ??

> 
> Finally, the server couldn't tell which SRU response would to give to
> encapsulate the diagnostic when it can't parse the request.
> 

Explain response, what else ??

If no valid operation is parsed (due to empty parameter SRU GET list), 
explain is assumed anyhow ..

Marc


> Rob
> 
> On Fri, 18 Aug 2006, marc wrote:
> 
>> Diagnostic missing for SRU SOAP malformed packages ??
>>
>> Upgrading a SRU GET/SOAP implementation from PHP4 to PHP5 for a
>> customer, I detect sometimes SRU SOAP posted XML packages, which
>>
>> - either are not XML at all
>> - or miss the correct SOAP envelopes
>>
>> Looking at the diagnostic list at
>>
>> http://www.loc.gov/standards/sru/diagnostics-list.html
>> (by the way - why is there no link from the frontpage
>> http://www.loc.gov/standards/sru/
>> to this useful page  ?? You have to go over
>> "Additional Information", "Info URi's",
>> "Diagnostic Reference"  to get there ..
>> )
>>
>> I can not find any error/diagnostic that fits. I suggest the addition of a
>>
>> number 9 "SOAP envelope XML coding error"
>>
>> in the general section (or a similar thing).
>>
>> And it strikes me that a similar diagnostic for wrong URL encoding of
>> GET/POST parameters might be a good thing also ??
>>
>> Marc
>>
>>
>>
>>
>> --
>>
>> 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
>>
> 


-- 

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