Difference in between pywb proxy responses from local or remote memento sources?

Hey all,

I’m working on providing pywb as a transparent proxy to a very custom, artist created browser made in 1997. The trick is to use a DNS server that points all possible domains to a pywb instance that’s running in forced proxy mode.

It works fantastically when accessing locally available web archives. However, when I use a memento-based fallback chain for any resources that are not contained in the local web archive, the requested resources are found, but the custom browser doesn’t like the responses and stops working.

When using regular browsers from that time (Netscape and Internet Explorer) there’s no problem with local or remote resources.

I know this will be very hard to debug, and for sure this is not an error in pywb. But I wonder if there’s any difference in how pywb serves resources depending on where the index or the WARC material is coming from?

Is there an option in pywb to set different logging levels for what is sent to the client?

OK, forget about this, the issue is the amount extra HTTP headers remote web archives are adding. :sweat_smile: I was able to remove them by adding a bunch of rem-header directives to uwsgi.ini. Now this old browser is happy!

1 Like