Page 1 of 1

413 Request Entity Too Large

Posted: Wed Sep 04, 2019 10:37 pm
by martien
Hello,

until this evening (last try ca. 17.45h) queries like
q=pn any "US20190102515 US20190102514 US20190102513 US20190102512 US20190102511"
were possible with up 10 publication numbers.

Now I get "413 Request Entity Too Large" if I use more than four numbers.
Did the actual maintenance change something?

Re: 413 Request Entity Too Large

Posted: Thu Sep 05, 2019 9:43 am
by EPO / OPS Support
Dear Martien,

Thank you for reporting this issue.
We will investigate and keep you posted.

Kind regards,
OPS support

Re: 413 Request Entity Too Large

Posted: Thu Sep 05, 2019 11:38 am
by martien
In the mean time I found out, that it is no problem for a search with EP-numbers:
pn any "EP3531850 EP3531849 EP3531848 EP3531847 EP3531846 EP3531845 EP3531841 EP3531839 EP3531837 EP3531836" works as before.

Regards, Martien

Re: 413 Request Entity Too Large

Posted: Fri Sep 06, 2019 7:12 am
by EPO / OPS Support
Dear Martien,

A first analysis shows that this affects US and WO.

Kind regards,
OPS support

Re: 413 Request Entity Too Large

Posted: Sat Sep 07, 2019 8:34 pm
by martien
The first query with 5 US-numbers and the 413 error sends the message
"Too many terms within a query. There can not be more than 20 terms in total"

Another "413 Request Entity Too Large " error I got with a family query:

Code: Select all

url:        https://ops.epo.org/3.2/rest-services/family/publication/docdb/WO.2006031917.A1/biblio,legal
err:        '413 Request Entity Too Large';
service:   family
data:      Please request bibliographic data in smaller chunks

Checking this on Espacenet (beta) the results shows 224 applications in the INPADOC family.
According to the OPS Ref. Guide 1.3.14, § 3.2.4, page 89, I understand there should be a
truncated result with a truncatedFamily-attribute as response.
(Not mentioned: how to get the rest of the family list.)

Kind Regards,
Martien

Re: 413 Request Entity Too Large

Posted: Mon Sep 09, 2019 7:40 am
by EPO / OPS Support
Hi,

This is a bit different; you are using family service with both available constituents and you are getting error because this service allows limited number of biblio returned. This is aditional limitation on top of potentially getting truncated family.

The example here is not truncated (database truncates only above 700 results extended family members or 1500 lines in response) but the family has over 200 members and only 100 biblio’s can be returned in Family service.

We recommend that in such cases you only search for family list and then take corresponding biblio from Published services where you can get up to 2000 results per query.

Regards,
Vesna for OPS support

Re: 413 Request Entity Too Large

Posted: Mon Sep 30, 2019 10:20 pm
by martien
Hi Vesna,

on the query

Code: Select all

q=pn any "US20190102515 US20190102514 US20190102513 US20190102512 US20190102511"
I just got

Code: Select all

413 Request Entity Too Large
Too many terms within a query. There can not be more than 20 terms in total
,
so the problem seems not to be solved yet.

Can you estimate, if/when the problem will be solved?

Thanks,
Martien

Re: 413 Request Entity Too Large

Posted: Tue Oct 01, 2019 6:18 am
by EPO / OPS Support
Hi,

This is waiting for the next maintenance release now. Please monitor our Announcements inn Forum for date of the release (I cannot tell you when that will be, sorry)

Regards,
Vesna for OPS support