Yes, there was a thread on this list where jidanni points to a possible solution for caching https (IIRR). Now i'm asking myself the same question....but i can't find this message. And I remember there's an archive somehwere, but i lost the link. Could somebody help me with this archive URL or just repeating what this idea was about ?
I've some thoughts about the problem. wwwoffle can't cache or modify pages received via https:// since this traffic is tunneled (that is, encrypted) between the web server and the browser-- is that right ? But, from a browser, i can save https pages on disk (with content directory). So there *is* a way for a user to get the unencrypted content, besides through the eyes. If wwwoffle could connect to this 'save as' output (pipe ? socket ?) and store the content normally, eg simply into the http directory, so that it can be re-called by just deleting the 's' from the https:// prefix. The browser would be like a (reverse) server then...weird. Is there at least theoretically a way for a proxy (or any user process) to get the 'https' page contents from the browser, without modifying the browser code ? Maybe a javascript 'bookmarklet' storing it into a 'wwwoffle-write' pipe ? ° /\/
