Dear OPS Team,
we receive a wrong response using the published-data request in DOCDB format for the publication US.10910944.B2
The request is:
http://ops.epo.org/3.2/rest-services/pu ... .B2/biblio
The Response from the OPS service is:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>OPS Error</title>
<link href="/style/common.css" media="all" rel="stylesheet" type="text/css"/>
<link href="/images/favicon.ico" rel="favicon"/>
</head>
<body lang="en" class="popup">
<div class="epoContentWrap clearfix">
<div id="pagebody">
<h1>Error</h1>
<h2>org.springframework.oxm.MarshallingFailureException: JiBX marshalling exception; nested exception is org.jibx.runtime.JiBXException: Error writing marshalled document</h2>
<!---->
</div>
</div>
</body>
</html>
As such HTML format error messages are not specified it is very hard to handle such responses in our backend programs. Would it be possible to wrap such error messages into a XML error message.
Many thanks
Thomas Stiefvater
Wrong response format error in published-data request
Re: Wrong response format error in published-data request
We have found the same problem requesting the publication of CN.110226207.A. It seems that this problem is not only an individual case.
Many thanks
Thomas Stiefvater
Many thanks
Thomas Stiefvater
-
- Posts: 1298
- Joined: Thu Feb 22, 2007 5:32 pm
Re: Wrong response format error in published-data request
Dear Thomas,
I just recreated your search in API Console and I cannot confirm the issue, I get both document, in DOCDB format Regards,
Vesna
I just recreated your search in API Console and I cannot confirm the issue, I get both document, in DOCDB format Regards,
Vesna
Re: Wrong response format error in published-data request
Dear Vesna,
I have also checked it again with the API tool and get the same error reponse as in our application. That means you are accessing the underlying database in a different way.
Request
Reponse:
Regards
Thomas
I have also checked it again with the API tool and get the same error reponse as in our application. That means you are accessing the underlying database in a different way.
Request
Code: Select all
GET /3.2/rest-services/published-data/publication/docdb/CN.110226207.A/biblio HTTP/1.1
Accept:
*/*
Accept-Encoding:
gzip
Accept-Language:
de
Authorization:
Bearer GdzNTZol2PyNwUSVl41BBllnYRDD
Host:
ops.epo.org
User-Agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:86.0) Gecko/20100101 Firefox/86.0
X-Forwarded-For:
87.139.117.70
X-Forwarded-Port:
443
X-Forwarded-Proto:
https
Code: Select all
HTTP/1.1 200 OK
Access-Control-Allow-Credentials:
true
Access-Control-Allow-Headers:
Authorization
Access-Control-Allow-Methods:
POST
Access-Control-Allow-Origin:
*
Cache-Control:
no-cache
Connection:
keep-alive
Content-Type:
application/xml;charset=utf-8
Date:
Fri, 19 Mar 2021 13:03:32 GMT
Pragma:
no-cache
Server:
Apache
Strict-Transport-Security:
max-age=31536000; includeSubDomains
Transfer-Encoding:
chunked
Vary:
Accept
X-API:
ops-v3.2
X-Elapsed-Time:
22
X-EPO-Client-IP:
35.231.184.45
X-EPO-Forwarded:
[87.139.117.70
X-IndividualQuotaPerHour-Used:
0
X-RegisteredQuotaPerWeek-Used:
153387832
X-Throttling-Control:
idle (images=green:200
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>OPS Error</title>
<link href="/style/common.css" media="all" rel="stylesheet" type="text/css" />
<link href="/images/favicon.ico" rel="favicon" />
</head>
<body lang="en" class="popup"><div class="epoContentWrap clearfix"><div id="pagebody">
<h1>Error</h1>
<h2>org.springframework.oxm.MarshallingFailureException: JiBX marshalling exception; nested exception is org.jibx.runtime.JiBXException: Error writing marshalled document</h2>
<!--
-->
</div></div></body>
</html>
Thomas
-
- Posts: 1298
- Joined: Thu Feb 22, 2007 5:32 pm
Re: Wrong response format error in published-data request
Hi,
Actually, the source is the same but I didn't display the result once I saw 200 successful status. I've asked colleagues on Friday already to look at it, I will provide you with an update once I get more info from them.
Thank you for reporting this and let me now if you get more
Regards,
Vesna for OPS support
Actually, the source is the same but I didn't display the result once I saw 200 successful status. I've asked colleagues on Friday already to look at it, I will provide you with an update once I get more info from them.
Thank you for reporting this and let me now if you get more
Regards,
Vesna for OPS support