On Sun, 7 Jul 2024 19:10:57 +0200 Rodrigo Arias <rodar...@gmail.com> wrote:
> On Sun, Jul 07, 2024 at 10:21:05AM +1000, Kevin Koster wrote: > >In addition to HTTP header feilds, it would be handy to assign > >rewrite rules according to HTTP status codes. I spend a lot of time > >browsing dead/dying websites so I'm always using the Wayback > >Machine. I'd like to use this system to process 404 (500, etc.) > >error pages through a program/script that adds a link at the top to > >look up the URL at the Wayback Machine. It might also check for a > >copy I've archived locally, if I get my website archives more > >organised, and link to that as well. > > Good idea, this should be doable with the rule mechanism. An > important consideration is to be able to quickly forward good > requests or responses, so we reduce the overhead in overall browsing. > > We could probably just hook it to >= 400 and then you handle those > broken responses as you want, while quickly forwarding 200 to Dillo: > > match http-status-code >= 400 action broken-page > > I think we may need to define several "tables" like in iptables so we > can have rules that handle the traffic at different stages. This one > doesn't require decoding the compressed content. That would be great. Provided it doesn't actually end up as complicated as iptables configuration of course. :) _______________________________________________ Dillo-dev mailing list -- dillo-dev@mailman3.com To unsubscribe send an email to dillo-dev-le...@mailman3.com
