whoogle-search/app
Ben Busby f22e5ac171
Catch and ignore unpickling errors in pip installs
This seems to be caused by an odd behavior related to Flask sessions and
instances of Whoogle installed via pip. I didn't investigate it too
much, since catching and ignoring the result doesn't impact Whoogle
functionality at all (configuration and session values persist as
normal). Since this doesn't affect non-pip instances, I don't believe it
to be a fault within Whoogle itself.

Fixes #765
2022-06-03 14:29:57 -06:00
..
models Support proxying results through Whoogle (aka "anonymous view") (#682) 2022-04-13 11:29:07 -06:00
static Fix german translation error (#742) 2022-05-02 11:56:21 -06:00
templates Render error message w/o `safe` filter 2022-04-26 09:28:05 -06:00
utils Ensure searches with a leading slash are treated as queries 2022-06-03 14:03:57 -06:00
__init__.py Use `lax` for session `SameSite` value (not `strict`) 2022-05-10 17:40:58 -06:00
__main__.py Swap out Flask's default web server for Waitress (#32) 2020-05-12 17:14:55 -06:00
filter.py Ensure searches with a leading slash are treated as queries 2022-06-03 14:03:57 -06:00
request.py Switch to defusedxml for xml parsing 2022-03-01 12:54:32 -07:00
routes.py Catch and ignore unpickling errors in pip installs 2022-06-03 14:29:57 -06:00