News for hackers. Stuff that matters.
Re:Show HN: RSS Search Engine by daviducolo on Wednesday May 08, 2019 @04:57AM (#19857066)
this is a simple reactjs app around my personal project feedi take a look at https://github.com/davidesantangelo/feedi
Re:Show HN: RSS Search Engine by stevekemp on Wednesday May 08, 2019 @10:01AM (#19858862)
I don't quite understand how the searching works; if I search for "Steve Kemp" I expect to find my own feed, or nothing. Yet instead I get results just including "Steve".

(Wrapping in quotes didn't make a difference, nor did adding AND in the middle.)

Re:Show HN: RSS Search Engine by pkd on Wednesday May 08, 2019 @08:00AM (#19857992)
You should configure your Rails application correctly for production. Right now it seems like it's considering all requests as local and returning the Rails exception page to me.
Re:Show HN: RSS Search Engine by daviducolo on Wednesday May 08, 2019 @08:07AM (#19858033)
if you try this https://feedi.me/search/entries?q=SEO&page=2 you receive an exception because Total are 10. I must improve exception management
Re:Show HN: RSS Search Engine by daviducolo on Wednesday May 08, 2019 @08:04AM (#19858019)
can you send me an example of your request?
Re:Show HN: RSS Search Engine by pkd on Wednesday May 08, 2019 @08:18AM (#19858097)
Absolutely. I'm talking about things that should 404 are actually raising exceptions. E.g. https://feedi.me/popular. I hit this link by mistake but that should return a 404 and not the exception page from Rails.
Re:Show HN: RSS Search Engine by pkd on Wednesday May 08, 2019 @08:24AM (#19858134)
This generally happens because config.consider_all_requests_local is set to true in production env. By default it should only be true in development and test.
Re:Show HN: RSS Search Engine by daviducolo on Wednesday May 08, 2019 @03:54PM (#19862271)
yes because the correct request is https://feedi.me/feeds/popular not "https://feedi.me/popular"
Re:Show HN: RSS Search Engine by pkd on Wednesday May 08, 2019 @07:26PM (#19863933)
Yes I understand that. But visiting your Rails app shouldn't bubble up the debugging info to your visitor in production.