Strongly recommend using Apache Tika[1] for this. It's industry standard for ubiquitous document text extraction. You can take the text output from Tika, chunk it with something like Chonkie[2], and embed it for your search index. -[1]https://tika.apache.org/ -[2]https://chonkie.ai/. - Source: Hacker News / about 2 months ago

Apache Tika could help extract the relevant bits of PDFs, couldnt it? https://tika.apache.org/. - Source: Hacker News / 12 months ago

Apache Tika has worked well for me in the past, ended up running it on an AWS Lambda https://tika.apache.org/. - Source: Hacker News / almost 2 years ago

If you accept running Java, the Apache Tika is extremely good at parsing content (https://tika.apache.org/). - Source: Hacker News / almost 2 years ago

Apache Tika can spit out text from lots of formats. I've used it with grep (or rg) to make a small scale searching of local folders. Tika does a really good job at OCR for finding if text is in a file. Source: about 2 years ago

HTTP was invented as a stateless protocol, which means that each request fully encapsulates all of the information necessary to return a correct response. So historically, web pages never had to worry about managing state - each request to a URL with parameters or with a form submission would receive a response with all of the HTML that the browser needed to render content. - Source: dev.to / 10 months ago

HTTP/1.1 was such a game changer for the Internet that it works so well that even through two revisions, RFC 2616 published in June 1999 and RFC 7230– RFC 7235 published in June 2014, HTTP/1.1 was extremely stable until the release of HTTP/2.0 in 2014 — Nearly 18 years later. Before continuing to the next section about HTTP/2.0, let us revisit what journey HTTP/1.1 has been through. - Source: dev.to / almost 2 years ago

On the one hand, it just seems natural that "upstream" refers to the inbound request being sent from one system to another. It takes effort (connection pooling, throttling, retries, etc.) to make a request to an (upstream) dependency, just as it takes effort to swim upstream. The response is (usually) easy... Just return it... hence, "downstream". Recall the usual meaning of "upload" and "download". Upstream seems... - Source: Hacker News / about 3 years ago

To me it sounds like you’ve not solved this as the config you’ve mentioned is about preventing “illegal” (none RFC7230 ) requests, it isn’t really related to the problem you posted. Source: over 3 years ago

The program you are using to send data to the server may or may not automatically determine the right content-type header for your data, and knowing how to set and check headers is an essential skill. To learn more about the HTTP protocol check out the MDN guide or read the official standard, RFC 7230. - Source: dev.to / almost 4 years ago