HTTP/1.1 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

Posts: 1
Joined: Tue May 06, 2014 12:10 pm

HTTP/1.1 413 Request Entity Too Large

Post by d.laredo » Tue May 06, 2014 12:21 pm


We are trying to work with epo search service and when we run the query we are getting 'HTTP/1.1 413 Request Entity Too Large' response. The query is:

Code: Select all

 ops . epo . org / 3.1 /rest-services/published-data/search/abstract,biblio,full-cycle ?q=q= ( ipc%3DB01D46)%20or%20(ipc%3DB01D47)%20or%20(ipc%3DB01D49)%20or%20(ipc%3DB01D50)%20or%20(ipc%3DB01D51)%20or%20(ipc%3DB01D53/34)%20or%20(ipc%3DB01D53/35)%20or%20(ipc%3DB01D53/36)%20or%20(ipc%3DB01D53/37)%20or%20(ipc%3DB01D53/38)%20or%20(ipc%3DB01D53/39)
Any help to know how to make dinamic searchs.


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

Re: HTTP/1.1 413 Request Entity Too Large

Post by EPO / OPS Support » Tue May 06, 2014 1:22 pm

Dear user,

As the error says, your query is too big and that is due to all constituents that you are using: abstract+ biblio + full-cycle. No searcher would actually make such query in practice because no one will go and read more than 100000 documents, so you would have to restrict your query in order to get only documents you want, without all the noise. Since OPS is now paying service (for downloading above 2,5 GB per week), you need to be even more careful with such random downloading because you will actually have to pay for every document you retrieve which means you should only be paying for those that you actually need.

This query is theoretically possible but you won't gain any use of it because OPS will only allow you to download/display first 2000 hits.

Another problem is that you are trying to use all three constituents which makes your request even bigger. If you choose biblio, you already have abstracts in biblio, so there is no need to add abstract constituent as well, and if you choose fully cycle then you get all biblio (and abstract, if available) for all available publication steps anyway. Only one constituent is actually needed.

OPS is not meant for such complex searches, same as Espacenet is not, in addition to that, OPS does not allow bulk downloading so even if you manage to make your query work, your search result is over 100000 hits from which only first 2000 you will be able to display.

You need to form your query in such way that the results will be manageable by the system and the end user. ... 01D53%2F39

For such huge queries you need to use professional search tools and those are usually not free of charge. In case of EPO, we offer GPI, but that is not a web-service as our OPS, but proper database for professional searchers:

More info on how to search OPS and Espacenet is available here: ... opic=index and ... ationscql
Kind regards,

OPS support

Post Reply