413 Request Entity Too Large

This space is made available to users of Open Patent Services (OPS) web-service and now also to users of EPO’s bulk data subscription products such as 14. EPO worldwide bibliographic database (DOCDB), 14.11 EPO worldwide legal status database (INPADOC), 14.12 EP full text data, 14.1 EP bibliographic data (EBD)and more.

Users can ask each other questions, exchange experiences and solutions, post ideas. The moderator will use this space to announce changes or other relevant information.
Post Reply

heltime
Posts: 15
Joined: Tue Mar 22, 2022 3:44 pm

413 Request Entity Too Large

Post by heltime » Wed Mar 29, 2023 12:54 pm

Hi, I'm trying to get patent family data of a patent, but OPS responds with 413 Request Entity Too Large. What does this mean in this context? Here a few example requests and responses:

Code: Select all

http://ops.epo.org/rest-services/family/application/docdb/EP.20177837.A/biblio

StatusCode: 413, ReasonPhrase: 'Request Entity Too Large', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:
{
  Date: Wed, 29 Mar 2023 11:25:51 GMT
  Connection: keep-alive
  Server: Apache
  X-Throttling-Control: busy (images=green:100, inpadoc=green:45, other=green:1000, retrieval=green:100, search=green:15)
  Strict-Transport-Security: max-age=31536000; includeSubDomains
  X-API: ops-v3.2
  X-IndividualQuotaPerHour-Used: 6015160
  X-RegisteredQuotaPerWeek-Used: 2644011
  X-EPO-Client-IP: 88.90.184.33
  X-EPO-Forwarded: [88.90.184.33]
  Access-Control-Allow-Methods: POST
  Access-Control-Allow-Origin: *
  Access-Control-Allow-Headers: Authorization
  Content-Type: application/xml;charset=UTF-8
  Content-Length: 222
  Content-Language: en
}

http://ops.epo.org/rest-services/family/publication/docdb/EP.3725778.A1/biblio

StatusCode: 413, ReasonPhrase: 'Request Entity Too Large', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:
{
  Date: Wed, 29 Mar 2023 11:27:43 GMT
  Connection: keep-alive
  Server: Apache
  X-Throttling-Control: busy (images=green:100, inpadoc=green:45, other=green:1000, retrieval=green:100, search=green:15)
  Strict-Transport-Security: max-age=31536000; includeSubDomains
  X-API: ops-v3.2
  X-IndividualQuotaPerHour-Used: 6015382
  X-RegisteredQuotaPerWeek-Used: 2644233
  X-EPO-Client-IP: 88.90.184.33
  X-EPO-Forwarded: [88.90.184.33]
  Access-Control-Allow-Methods: POST
  Access-Control-Allow-Origin: *
  Access-Control-Allow-Headers: Authorization
  Content-Type: application/xml;charset=UTF-8
  Content-Length: 222
  Content-Language: en
}


http://ops.epo.org/rest-services/family/publication/docdb/EP.3725778.B1/biblio

StatusCode: 413, ReasonPhrase: 'Request Entity Too Large', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:
{
  Date: Wed, 29 Mar 2023 11:28:13 GMT
  Connection: keep-alive
  Server: Apache
  X-Throttling-Control: busy (images=green:100, inpadoc=green:45, other=green:1000, retrieval=green:100, search=green:15)
  Strict-Transport-Security: max-age=31536000; includeSubDomains
  X-API: ops-v3.2
  X-IndividualQuotaPerHour-Used: 6015604
  X-RegisteredQuotaPerWeek-Used: 2644455
  X-EPO-Client-IP: 88.90.184.33
  X-EPO-Forwarded: [88.90.184.33]
  Access-Control-Allow-Methods: POST
  Access-Control-Allow-Origin: *
  Access-Control-Allow-Headers: Authorization
  Content-Type: application/xml;charset=UTF-8
  Content-Length: 222
  Content-Language: en
}


EPO / OPS Support
Posts: 1298
Joined: Thu Feb 22, 2007 5:32 pm

Re: 413 Request Entity Too Large

Post by EPO / OPS Support » Wed Mar 29, 2023 5:09 pm

HI

That happens in a big family or truncated family, so its quite common in this service. The solution is only to query family members, get a list or their numbers and then query biblio of those members via Published Service with Biblio instead.

Regards
Vesna for OPS support


heltime
Posts: 15
Joined: Tue Mar 22, 2022 3:44 pm

Re: 413 Request Entity Too Large

Post by heltime » Fri Mar 31, 2023 7:28 am

Yep, that works, thanks!


Post Reply