Re: "pre-treating" documents from certain remote URLs before a web browser renders them

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, May 17, 2018 at 03:40:24PM +0300, Reco wrote: [...] > Squid can do it. It was called SSL Bump in old (pre 3.4) Squid, now they > renamed it to SSL Peek and Splice - [1]. Thanks! - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12

Re: "pre-treating" documents from certain remote URLs before a web browser renders them

Hi. On Thu, May 17, 2018 at 08:49:04AM +0200, to...@tuxteam.de wrote: > On Wed, May 16, 2018 at 07:35:51PM -0700, Kushal Kumaran wrote: > > [...] > > > You should note that HTTP-proxy based systems will not be able to do any > > inspection or modification of traffic for sites using

Re: "pre-treating" documents from certain remote URLs before a web browser renders them

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, May 17, 2018 at 07:52:55AM -0400, Celejar wrote: > On Thu, 17 May 2018 08:49:04 +0200 > wrote: [... proxy as SSL endpoint...] > > I don't know whether privoxy or squid can do that (I'd love to know, > > mind you, but days

Re: "pre-treating" documents from certain remote URLs before a web browser renders them

On Thu, 17 May 2018 08:49:04 +0200 wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Wed, May 16, 2018 at 07:35:51PM -0700, Kushal Kumaran wrote: > > [...] > > > You should note that HTTP-proxy based systems will not be able to do any > > inspection or

Re: "pre-treating" documents from certain remote URLs before a web browser renders them

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, May 16, 2018 at 07:35:51PM -0700, Kushal Kumaran wrote: [...] > You should note that HTTP-proxy based systems will not be able to do any > inspection or modification of traffic for sites using HTTPS. This is true... and then it's not :-)

Re: "pre-treating" documents from certain remote URLs before a web browser renders them

davidson writes: > On Tue, 15 May 2018, davidson wrote: > >> I have a problem: The more frequently I browse a web site, the more I >> notice all the things I hate about its web pages. >> >> And I seem to have a partial solution to this problem: I can make XSLT >>

Re: "pre-treating" documents from certain remote URLs before a web browser renders them

On Tue, 15 May 2018, davidson wrote: I have a problem: The more frequently I browse a web site, the more I notice all the things I hate about its web pages. And I seem to have a partial solution to this problem: I can make XSLT stylesheets[1] that will transform a web page A, as received from

Re: "pre-treating" documents from certain remote URLs before a web browser renders them

On Tue, May 15, 2018 at 12:58:04AM +, davidson wrote: > And I seem to have a partial solution to this problem: I can make XSLT > stylesheets[1] that will transform a web page A, as received from a > remote site, into a XHTML document B that better suits my purposes.[2] > I find it entertaining

Re: "pre-treating" documents from certain remote URLs before a web browser renders them

On Tue, 15 May 2018 14:52:16 +0300 Reco wrote: > Hi. > > On Tue, May 15, 2018 at 12:58:04AM +, davidson wrote: > > I would like to launch a web browser[3], browse pages at domain X, and > > know that when I go to http://X/page, or https://X/page, etc, the > >

Re: "pre-treating" documents from certain remote URLs before a web browser renders them

On 15.05.2018 05:58, davidson wrote: > Do I want a local proxy server that I can instruct to apply > appropriate transformations to documents received from certain > domains? This seems sensible, but I haven't examined too deeply what > is available along these lines, and I would rather not spend

Re: "pre-treating" documents from certain remote URLs before a web browser renders them

Hi. On Tue, May 15, 2018 at 12:58:04AM +, davidson wrote: > I would like to launch a web browser[3], browse pages at domain X, and > know that when I go to http://X/page, or https://X/page, etc, the > browser will render not the page served from the remote site, but will > render

Re: "pre-treating" documents from certain remote URLs before a web browser renders them

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, May 15, 2018 at 12:58:04AM +, davidson wrote: > I have a problem: The more frequently I browse a web site, the more I > notice all the things I hate about its web pages. [...] I think you're looking for a HTTP proxy. Cheers - -- t

"pre-treating" documents from certain remote URLs before a web browser renders them

I have a problem: The more frequently I browse a web site, the more I notice all the things I hate about its web pages. And I seem to have a partial solution to this problem: I can make XSLT stylesheets[1] that will transform a web page A, as received from a remote site, into a XHTML document B