Dan Jacobson <[EMAIL PROTECTED]> writes: > I am all excited about using WWWOFFLE with https. I have installed the > new .deb. > I wish /usr/share/doc/wwwoffle/README.https.gz would clarify if I am > just dreaming about: > * browsing https can be just like http: > queue requests offline, read them later back offline. > Which of > https_proxy=http://localhost:8443/ > https_proxy=https://localhost:8443/ > https_proxy=http://localhost:8080/ > https_proxy=https://localhost:8080/ > is correct for exporting in .bash_profile? Yes I am that dumb.
The third one "https_proxy=http://localhost:8080/"; is probably the correct one if your browser accepts a variable of this name. If you are proxying https connections then you need to use port 8080 which is the WWWOFFLE proxy port and not 8443 which is the WWWOFFLE https port. You can access the pages securely through https://localhost:8443/ but it is not the proxy port. This is due to the way that https works, it requires a full negotiation of security credentials before you can tell the server what you want. For proxying there is no security negotiation by the proxy, just a transparent connection from one side to the other. > Should wwwoffle.pac be updated? I have not done that because I don't know if it works and if it does then it would hide from the user what is happening. I want to make sure that WWWOFFLE does not proxy https for the user without them knowing it. Obviously I cannot do this for every user, but I want to make sure that anybody configuring WWWOFFLE must make positive actions to make https proxying work. > Please don't make me see another "Firefox can't establish a connection > to the server at panel.dreamhost.com" message, offline or on. > > What about > Proxy > { > <http://*:/*> proxy=proxy.apol.com.tw:8080 > } > Should I add a https version or does that depend on that company or do > I not grasp a basic concept and if so never mind. You could add a line like: ssl = proxy.apol.com.tw:8080 but that only works if they support https proxying. Even if it does work there is no benefit since they cannot be caching the https session so you have no advantage from using their proxy. This option is really only for people working where there is a very tight firewall policy that forces proxying of https connections. > (P.S., for plain old http, the exact words > "http_proxy=http://localhost:8080/"; aren't in the documentation > anywhere either.) There used to be a section in the README file that described how to configure browsers to use WWWOFFLE. It described the http_proxy variable and other methods. I removed it because it was too complicated, there are too many browsers and too many different ways to configure them. The instructions in README now tell users to consult the instructions for their browser. -- Andrew. ---------------------------------------------------------------------- Andrew M. Bishop [EMAIL PROTECTED] http://www.gedanken.demon.co.uk/ WWWOFFLE users page: http://www.gedanken.demon.co.uk/wwwoffle/version-2.9/user.html
